Have a look at these for some ideas http://www.nabble.com/How-to-for-building-for-different-environments-t494243.html#a1343428
http://www.nabble.com/How-to-use-different-context.xml-files--t444332.html#a1213765 On 24/01/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi there, > > Firstly, m2 rocks, it took some time to implement but what a great result. > Much faster, clearer esp. for web projects. > > So my question, I have read the doco, reviewed the lists and found many > things that might fit this bill and am confused as to best practice. I > wonder even if an extra plug-in might be needed and if so, will write it. > > Here is the issue: > > deploy targets: > > test > production > > differences: > > src/main/webapp/WEB-INF/applicationContext.hibernate.xml > src/main/webapp/WEB-INF/default.properties > > So between the two WARs generated for these environments, I need to have > different settings in these xml/properties files. I figure that I could : > > 1. Create an overlay directory tree per env. and sort of merge the overlay > over the standard WAR. > 2. Use profiles to somehow select one subdir for resources vs another. > 3. Something else, much smarter. > > Any ideas? It doesnt seem to be covered clearly in the doco or miniguides. > Unless of course I missed it! > > If I was to write a plugin I would be looking to call this sort of thing: > > m2 -Dship.to.env=test package > > which would merge into the WAR the test environment differences and > probably call the result myapp-test.war > > ATB > > Stuart Guthrie > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
