[
http://jira.codehaus.org/browse/MVERSIONS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=239766#action_239766
]
Lars Corneliussen commented on MVERSIONS-121:
---------------------------------------------
Maven doesn't support a combination of classifier and build-number. Every
"build-number" with alphanumeric characters is completely treated as
classifier. There are proposals to change this, though:
http://docs.codehaus.org/display/MAVEN/Versioning
But we need to release things named "1.1-qa00015". The 15 is the build-number,
"qa" is kinda the qualifier and stands for 'qa/test release'.
We run branches for major versions. Minor version can change within a branch.
The developer decides when to increase the minor version.
The system creates those qa releases, when issues are set do done.
It is important, that the system doesn't touch the branch's source-code because
then, the developer would need to update the working copy too often. Instead
all developers run SNAPSHOT versions and SNAPSHOT dependencies. The CI server
builds and deploys that for continuous integration. For test, we then set the
version to qa+build number and automatically resolve all dependencies to the
highest qa-release available. This is, where we specify a regex 'qa/d/d/d/d'...
We found that to be the easiest way to achieve the goals. Do you have other
ideas on how to handle this scenario?
Idea: What about a new goal "use-classified-releases"?
> Allow "versions:use-releases" to update a version to qualified releases as
> for example "alpha-2" or "beta-3"
> ------------------------------------------------------------------------------------------------------------
>
> Key: MVERSIONS-121
> URL: http://jira.codehaus.org/browse/MVERSIONS-121
> Project: Maven 2.x Versions Plugin
> Issue Type: Improvement
> Reporter: Lars Corneliussen
>
> As part of a automated build, we need to update dependency versions to
> qualified releases. In our case we do automatic releases based on some rules.
> But we do not really increase the version numbers, because the snapshot
> version should stay the same all the time. Its actually the same thing as
> releasing numbered alpha- or betas-...
> Given "mygroup:mylib:1.0-SNAPSHOT having an dependency on
> mygroup:mydep:1.0-SNAPSHOT":
> Now, if I want to be able to release mylib:1.0-r00015 (<- Build Number) it
> should update to the latest r**** of mygroup:mydep:1.0...
> Currently we have a patched version of maven-versions that allows following
> command:
> {code}
> mvn versions:use-releases -DallowQualifiedReleases=true
> -DqualifierIncludesList=r\d\d\d\d\d -DincludesList=mygroup:*
> {code}
> qualifierIncludes/Excludes are currently regex.
> If you find that interesting to be added to Maven Release I'd really be happy
> to provide a patch and some tests. You can find the current implementation on
> github:
> http://github.com/lcorneliussen/apache-versions/commits/use-qualified-releases
> A patch to be applied with TortoiseSVN is available here:
> http://lcorneliussen.de/utils/git-svn/github.com/lcorneliussen/apache-versions/commits/use-qualified-releases
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
