I currently have a system that has a single
Maven build. It contains many modules, with only one shared library between all of them. I have it setup where I can do a build of all of the modules at once.
My project is setup as such:
Web Application and service end pointsShared libraryClient Project1Client Project2
Client Project 2 contains tests that require the web application to be deployed and working. If the web application's
test endpoints fail, then I'm ok with the Client-Project2 not to be built.
[Please forgive me with all of this detail.. I'm a little bit lost on whats the best practice here]
So the questions I have:
How would I build the Java web application and keep a separate configuration? (I can't just store it in the DB, because the DB connection string can change based on where its deployed... and it doesn't fix the configuration deal) I'm also reluctant to hard code the database reference within the build. (Via resource filtering) How would I force a deploy within Maven prior to moving to the next project?