David Cao wrote:
Thanks for the help. I had studied all these option very carefully
before. But they won't work for us.
All our sources are in source control system. The requirement is that anybody can reproduce the build without knowing the application by retrieving the sources. project.property, build.property have static relationship which can not be changed by command line. The -Dproperties is designed to set a / few system property, it will work. In our case, it is not practical. Any more?
-David
Here is what I do:
project.properties -- is in CVS and provides default values.
build.properties -- is never checked into CVS and allows developers to override. Developers can do builds using Maven command line or their own scripts.
For production build or test build, provide a script that gets checked into CVS. That script invokes Maven with explicit property overrides.
Thus the release process is:
1. Fetch code from CVS according to release label. 2. Invoke the "buildRelease" script.
--
Erik Husby
Senior Software Engineer
Broad Institute of MIT and Harvard Rm. 2192 320 Charles St, Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, email: [EMAIL PROTECTED] AIM: ErikAtBroad
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
