I think the first thing you should do is compare what you define as
"release" and compare it with what the Release plugin does.  "Release" is a
loaded term for everyone making software.

A Release in Maven means it's a fixed point in the lifecycle of the
artifact.  In a strictly maven-versioning term, you will never make two
releases of the same version number (where the version number is not a
SNAPSHOT release).

Typically, when you do a release, the target and next version numbers are
supplied.  And this doesn't lend itself to an automated process.  I'm kind
of reading inbetween the lines with your emails about doing "a release
build every night, which takes the latest successful continuously build
baseline".  Is there a reason why snapshot releases for these nightly jobs
are not sufficient?

Thanks,
Ed


On Wed, May 23, 2012 at 1:14 AM, hujirong <[email protected]> wrote:

> Hi
>
> I just set up a snapshot build, I call it continuously build. A "mvn
> deploy"
> will upload the snapshot to the Nexus repository. Here is the project
> pom.xml:
>
>        <groupId>com.nbfg.max.wesb</groupId>
>        <artifactId>CDIPubSubMgmtMed</artifactId>
>        <version>0.0.1-SNAPSHOT</version>
>        <name>CDIPubSubMgmtMed Mediation</name>
>
> Now I want to know how to do a release build in Maven. I am using RTC and
> for other build tools like CruiseControl, here is what we do:
>
> 1. We have a continuously build workspace/branch to build the code every 10
> minutes. Every build has a baseline created.
> 2. We do a release build every night, which takes the latest successful
> continuously build baseline.
>
> How can I do something similar in Maven, or how does Maven do a release
> build?
>
> Thanks
> Jirong
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/How-to-do-a-release-build-in-Maven-tp5709440.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to