Eric, Thanks for your suggestions. each developer is working more than 5 projects as same time. All the build script have to be in CVS. This may not work well. However, do you know if this will work:
1 Check in a build-dev.property. 2 When called maven, if <project>/build.property does not exist, copy from build-dev.property, then restart maven. We have enough resources to develop our own plugin, as far as we know it is going to work. -David On Wed, 2005-02-23 at 11:17, Erik Husby wrote: > 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. -- David -- Powered by Thinking Lead Java Engineer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
