On Wed, Apr 18, 2012 at 4:33 PM, Andrew Hughes <[email protected]> wrote: > Hi All, > > > We have decided that we would like to release configured artifacts from our > scm. I am looking at the most suitable way to do this with maven3. > > Use Case: > We have released v2.5.1.0 or our webapp. We would like to take v2.5.1.0, > make a change to the configuration (i.e. a <property>), check that into the > SCM and then release that as v2.5.1.1 (or we could even use > 2.5.1.${buildNumber}) > > Additionally: > We need to release different artifacts for each release for different > target environments LATEST, DEV, UAT, PRODUCTION. > > > > What is the best way to achieve this, and (if possible) are classifiers a > suitable way to distinguish LATEST, DEV, UAT, PRODUCTION configured > artifacts?
Have you read the freely available books over at http://maven.apache.org/articles.html? classifiers are not meta data about your released artifact. >From http://maven.apache.org/pom.html The classifier allows to distinguish artifacts that were built from the same POM but differ in their content.... You will need to use some internal mechanism for tracking this meta data. That's your PMs job. To make a new build, Create a branch 2.5.1.1 from the tagged version 2.5.1.0. Make your changes on the branch. Check them in. Run mvn release:prepare and mvn release:perform to generate 2.5.1.1 (or whatever release process you use that originally create 2.5.1.0) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
