Am 29.02.2012 22:33 schrieb "offbyone" <[email protected]>: > > I have no interest in using JNDI.
You certainly don't need to. Pick any mechanism you like to configure your application according to the needs of your runtime environment, as long as you do it by configuration at *runtime* (not compile time). Would Microsoft sell a " Windows 7 for networks having their DNS server at 192.168.1.1" and bake this information into win32.sys on their product DVDs? Certainly not. They sell "Windows 7" and let you configure the DNS server address at runtime. If you really want to create stage specific rollout artifacts using maven, that's also okay, but it's best handled as different modules. Each module would include the common artifacts like jars etc. and put it into a zip file or rpm or whatever you like, and ultimately add the stage-specific configuration *data* which is later used by the application. > Could someone please address my question > regarding profiles? Maven profiles are intended to be used to make your build working in different *build* contexts. Examples: use host xy as repository manager when building at work, use abc when at home. Don't use them to differentiate between different *runtime* environments of the application you are building. Keep your artifacts independent of application configuration as far as possible. Just my 0.02€ Best Ansgar > > -- > View this message in context: http://maven.40175.n5.nabble.com/using-build-profiles-for-WAR-plugin-tp5525954p5526140.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
