On 27/12/2012 2:02 PM, Laird Nelson 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
You can move the configuration to JNDI or other methods that get
configuration out of the war file but still accessible to the application.
http://blog.artifact-software.com/tech/?p=150
http://blog.artifact-software.com/tech/?p=58
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
