On Tue, Mar 1, 2011 at 9:27 AM, Greg Akins <[email protected]> wrote:
> Thanks for everyone's advice. > > The CM, Team Lead and I are going to go over some options next week. > I'll update the group and will probably have some more question when > we decide on the best options. > > > I'm back to this finally. I have a tentative plan, but am hoping I can get a bit more input. What do you all think of the following? We decided it would be best to have a WAR per project and keep all our configs in separate locations (since they simple need to be tarred up and sent to sysadmins, probably not Maven projects) So source control might be configured like what's shown below. One thing I can't quite get my head around is how I can keep a development config in the Maven projects so a developer can run from Maven without worrying about extra steps to "configure" the application, but ensure that those dev configs won't get deployed to other QA/Stage/Production environments. -- ProjectA (Maven) -- ProjectB (Maven) -- Config -- ProjectA.properties -- ProjectB.properties -- deploy.sh -- Greg Akins http://twitter.com/akinsgre
