On 11/03/2011 1:23 PM, Greg Akins wrote:
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)
You would be surprised at the amount of discussion there is on this point.
You have it right.
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.
Keeping your server(localhost, all the test, all the productions)
configurations out of your war files is the right way to go for exactly
the reason that you identified.
Getting everyone to use the same localhost configuration is probably the
hardest part but really makes the team function more effectively once
you have it in place.
JNDI is a good way to manage server confiurations.
Separating Deployment from Development with JNDI
http://blog.artifact-software.com/tech/?p=58
This has been discussed here at length and you will find other good
approaches to this problem.
It is always good to bear in mind that whatever you need to do, there is
already a "Best Practice" available through this forum.
If you take a second to describe the high level problem that you are
trying to solve, you will generally get a better answer than you will if
you ask a low level technical question.
Maven is incredibly flexible and some of the guys here can get Maven to
do anything you can think of, but often the right answer to the wrong
question can lead to a horrible waste of time and energy before the real
nature of the problem finally comes to light.
Ron
-- ProjectA (Maven)
-- ProjectB (Maven)
-- Config
-- ProjectA.properties
-- ProjectB.properties
-- deploy.sh
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
