We build wars - but keep the config outside. We use a startup class to reference them and load them accordingly.
Are you saying "unless of course you happen to work for a company that is forced to produce to the exacting standard <artifacts>"? I don't know anyone following the rules 100% - including any of the containers available today.... On Thu, Dec 27, 2012 at 2:02 PM, Laird Nelson <[email protected]> wrote: > On Thu, Dec 27, 2012 at 7:46 AM, Maven User <[email protected]> > wrote: > > > AHHHH - yes, all your "configuration" should be OUTSIDE your war/ear/jar > > files! > > > > Don't repackage per env!!!! Also, don't force someone to unfurl your > > artifact, alter config, then re-roll it.... > > > > Right, unless of course you happen to be producing Java EE-compliant > artifacts such as .war and .ear files, in which case you have no choice, as > locating the configuration inside the artifact is mandated by the > specifications. However, even in such cases it's better to build separate > projects or war overlays or approaches like that than to abuse profiles. > > Best, > Laird > > -- > http://about.me/lairdnelson >
