Brett, thanks for the answer.
Tough, I think I should expain myself better ... see below
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
I ensure all differences are externalised from the WAR file. For the
appservers
we use (resin, tomcat), anything in web.xml can be put
A lot of people have these issues, so don't feel strange.
I see two ways to do this and I think Chuck Daniels covered more in his
latest
post.
1) Just like you can with Ant, create parametrized variables in
different config
files. Then work with your maven.xml to ensure that you build
11:06 AM
To: Maven Users List
Subject: RE: Deploy a webap to multiple environments (test,
pre-prod, prod)
This is also a question I've been meaning to ask because I
don't know if the technique I use is reasonable. Anyway,
here's what I do to create distributions for various target
Daniels [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 10, 2004 11:06 AM
To: Maven Users List
Subject: RE: Deploy a webap to multiple environments (test,
pre-prod, prod)
This is also a question I've been meaning to ask because I
don't know if the technique I use is reasonable. Anyway
Very good pointers, thanks a lot !
- Original Message -
From: Tim Shadel [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Thursday, June 10, 2004 8:21 PM
Subject: Re: Deploy a webap to multiple environments (test, pre-prod, prod)
Have you looked through Vincent Massol's
Hello,
I recently read a thread about this subject, but was not entirely convinced
by the answer.
I think this is a very common problem : you develop a webapp, and you have
to deploy it on multiple configurations : generally one for each
test-process environment : internal ( integration server
I ensure all differences are externalised from the WAR file. For the appservers
we use (resin, tomcat), anything in web.xml can be put outside the webapp and
added to it (Context definition in server.xml, web-app in resin.conf). So
configuration goes into JNDI environment entries, context-params,
