On 13 Nov 2010, at 2:37 AM, Christopher Hunt wrote:
Please correct me if I do not have this right, but in effect the
requirement is to take a snapshot release, the developer do their
testing and then, if satisfied, release it in effect by renaming the
artifact to drop the "-SNAPSHOT"? My apologies if this is an over
simplification, but if it is indeed the case then I think there is a
flaw. Just because the developer has done their testing doesn't mean
that everyone in the team has done their testing.
One of the things that needs to be kept in mind also is that SNAPSHOT
means the following:
"All bets are off. This was probably created from someone's non-
checked-in working copy. The build is definitely not repeatable, don't
even try think it is, as if you do you're fooling yourself".
Dropping the -SNAPSHOT just means mayhem.
I think the cleanest way for maven to do CD is to create a plugin that
slots in where you would normally use maven-release-plugin, and when
invoked does this:
- Checks out a pristine copy of the latest trunk or branch (or
optionally a user specified revision).
- Checks all files are checked in as maven-release-plugin does now,
fail if not.
- Sets the version number of the pom to match the revision number in
scm, taking out the SNAPSHOT.
- Runs the build.
- Runs the tests.
- Runs "mvn site"
- Runs "mvn deploy" and "mvn site-deploy"
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
