-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplify the installation process #50
Comments
I think I can easily implement a jetty:run maven target to ease application testing. I just need some time and motivation to work on it. I'll post messages here if there are enhancements on this point. |
I may open a PR for it to have a simple command line util to initialize the database |
Update about the installation process, without any other requirements than a running maven: Build all the codebase (with JDK 7) Once maven_artifact_notifier database is created, owned by maven_artifact_notifier, with password maven_artifact_notifier: run this command in maven-artifact-notifier-init folder: I continue to work on a jetty:run step. I'll report all this in the documentation once tested, and I would be happy to receive your feedback. JDK8 build is a later target as it needs to work on owsi-core build also (NB: only build requires JDK7; code can be run with JDK8) |
Updated process: Build all the codebase (with JDK7) mvn -Pdevelopment -DskipTests clean install Once maven_artifact_notifier database is created, owned by maven_artifact_notifier postgresql user, with password maven_artifact_notifier: run this command in maven-artifact-notifier-init folder: mvn exec:java -Dexec.mainClass="fr.openwide.maven.artifact.notifier.init.MavenArtifactNotifierInitFromExcelMain (this step requires feature-50-dev-tooling branch)
Application is available at http://localhost:8080; default login/password is [email protected]/admin. @spyhunter99 can you provide me some feedback about this process ? NB: feature-50-dev-tooling branch includes postgresql 9.6 fix. |
first of all, thanks for the super quick turn around. |
Error on my side. I'm happy you find the correct command. The command is (and jetty:run-war is surely quite similar): mvn jetty:run For additional questions, I think ticket is the best way to share and agree on the good solution. On this subject (project initialization), I'll welcome a PR on README.md or a new wiki page. Once the new content created and added, we'll see how to organize all the existing documentation on initialization. |
does this work? |
instead of relying on an ide, adding some maven configuration bits so that the installation process and can scripted without a full dev environment
The text was updated successfully, but these errors were encountered: