Michael-O, how do you choose what webapp use? Manually?
Ivo On Mon, May 27, 2013 at 2:33 PM, Michael-O <[email protected]> wrote: > Am 2013-05-27 17:20, schrieb Alberto Ivo: > > Hello, >> >> I have two different web.xml files. One for Developers and another for >> Production. >> >> Today I manually rename the file to use in develop enviroment and >> production. I would like to know how can I automatize the build using >> Maven >> Profile (or any other plugin). Is that possible? >> > > We do have this kind setup for years. It seems to me as the best approach > at the moment. This is how I solved it: > > webapp-parent > |- webapp-prod > |- webapp-test > |- webapp-qa > `- webapp-localdev > > The main artifact is webapp-localdev. Suited for the local developer. > Both prod and test do depend on the webapp-localdev artifact and solely > include different config files like web.xml, context.xml, spring.xml, etc. > The entire rest is performed by/through war overlays. I do receive maximum > flexibility with minimum effort. > > More over, we do have appropriate profiles in prod and test for different > Tomcat instances to deploy to. > > Using profiles for config management is a dead end idea and leads into two > problems: > > 1. You are constantly jumbling with different profiles > 2. You CANNOT reasonable deploy all configured webapps to your corporate > Nexus instance. If you do that somehow and you are breaking the > convention: one artifact -- one file > > Trust me, I evaluated the profile idea and it led to a lot of trouble. > > Michael > > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org<[email protected]> > For additional commands, e-mail: [email protected] > >
