I'm working on a software project (a cms with several web applications using struts and ejbs on the backside with 4 involved servers); up to now we use a lot of different tools for the build process (with ant as central tool). With the time we got some problems with the technical project organization: see the list at http://maven.apache.org/goals.html :-). Now starting a new subproject it would be a good time to rethink the whole thing so I took a fair amount of time to look for a better solution. Maven matches almost perfect, but there is one question I couldn't find an answer:
At the moment for the release build we have few properties-files containing some specific information for our production, integration and test environment (host names, ports, mail addresses etc.). These files are read by ant and during the build process the source files (properties, descriptors etc.) are written for the correct target environment.
How would an experienced maven user run builds for different environments? Would one add this ant logic just to maven.xml?
Thanks in advance
Peter H�berli
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
