Fred,
This kind of problem is generally solved using build profiles in Maven. The
'Better Builds with Maven' book covers this topic (free from
http://www.mergere.com/ ).
A good starting point is here:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
and here:
http://docs.codehaus.org/display/MAVEN/Build+Profiles
We use profiles to capture customisations and modifications to webapps in
terms of branding and configuration for different customers and their
environments. So we have profiles unix,windows which are mutually exclusive,
profiles dev,test,live which are mutually exclusive and then
custA,custB,custC profiles which are also mutually excluive. When we are
ready to release we build against (for example) unix,live,custA profiles.
HTH
Kieran
----- Original Message -----
From: "badaud" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, June 06, 2006 1:34 PM
Subject: Best practices for multi-flavour build?
I have a project for multiple clients. Each client must receive a
ready-to-deploy package of ear files. The jar and war contained in those
ear
files are usually just different by a few configuration files (but the
structure and the changes in these files can be quite complex).
Right now, we have a pesky ad hoc ant file, with ad hoc file extensions,
copy operations, separate Svn branches, a nightmare to maintain (not to
mention the long, tedious, manual and error prone build process).
I had some enjoyable experiences in the past with Maven and I'd like to
make
the move for this project too. I'd also like to have all those config
files
maintained in the trunk tree.
What would be the best way to :
- store and maintain those config files?
- easily generate one build for one client and another build for another
client?
Thanks for your advice
Best regards,
Fred
--
View this message in context:
http://www.nabble.com/Best-practices-for-multi-flavour-build--t1741483.html#a4732364
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
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]
