I'll admit knowing this was a loaded question. I've previously solved this via a separate configuration artifact.
I was just shocked to see how m3 doesn't allow the import of property files anymore the way 2.2.1 did. Thanks again all - I appreciate it! On Mon, Sep 19, 2011 at 5:19 PM, Wayne Fay <wayne...@gmail.com> wrote: > > How does this work when you have to deploy the same artifact to 10 > different > > environments? > > > > 10 profiles and build the artifact 10 times? > > We get this question so often on this list, and similar questions. You > should check the archives for various comments. > > The standard answer is "use JNDI" or some other DI > technique/framework. Bundle all environment settings into the artifact > and use some method to tell your app or app server which settings to > use for this specific server. Or extract all settings into a single > "configurations" artifact if you'd prefer. > > This also guarantees that the artifact you perform QA on is identical > (same code etc) to the artifact you deploy to PROD which is a > requirement for most sensibly-defined environments. If you build 10 > artifacts (one per environment) as you suggested then there is no such > guarantee. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
