I'm not quite sure what the accepted "best practices" are here or if
this is intended to be implied by Dion's suggestion, but, in addition
to putting the logic into a plugin, I suggest that you create a
separate module for each target environment. Each such module would
contain the appropriate property files for the target environment, and
building in that module would assemble the project customized for the
target environment.
thanks
david jencks
On Aug 22, 2004, at 7:03 AM, Dion Gillard wrote:
You would typically encapsulate the build knowledge into a plugin and
only specify properties for the environment.
On Sun, 22 Aug 2004 15:52:34 +0200, Peter H�berli <[EMAIL PROTECTED]>
wrote:
Hi,
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]
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
