You can use WAR overlays
[http://maven.apache.org/plugins/maven-war-plugin/overlays.html] for
making different war project for different distributions and also
different EAR projects to match needed WAR project.
rgds,
Markku
On 21.3.2011 17:56, Sam Adams wrote:
We have slightly different configurations that we need to test. For
this very reason we need to build and test different profiles. This
can include different web.xml files so I don't think externalising is
an option in this case.
Thanks,
Sam
On 21 March 2011 15:44, Wendy Smoak<wsm...@gmail.com> wrote:
On Mon, Mar 21, 2011 at 11:28 AM, Sam Adams<sbad...@gmail.com> wrote:
This is exactly what I'm trying to do. Why is this not a good idea and
what are the alternatives?
Depends on *why* you're trying to do that, which is why I asked what
problem you're trying to solve.
In general... either externalize the configuration or pack it all
inside and use something that can select the right file so that you
move the exact same war through the (I assume) different environments.
If you build a war for QA, test it, and then build a war for
production and deploy it... what have you *really* tested?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
