maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey De Smet (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT
Date Thu, 04 Aug 2011 12:26:42 GMT

    [ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274991#comment-274991
] 

Geoffrey De Smet edited comment on MRELEASE-699 at 8/4/11 7:26 AM:
-------------------------------------------------------------------

I can't use the release:prepare goal for various reasons [1],
but when I am releasing, I do need to be able to change all my versions from SNAPSHOT to release,
tag and deploy and then from release to SNAPSHOT again.

[1] Here's why I can't use the release:prepare goal:
- Our project has several git repositories with SNAPSHOT dependencies between them: https://github.com/droolsjbpm
(guvnor depends on drools, drools depends on droolsjbpm-knowledge, ...). Having them all in
a single git repo (of 1.2 GB) was unworkable for many reasons, yet for the time being they
do continue to share the same release lifecycle.
- We use tycho for our eclipse plugin (see droolsjbpm-tools). The release plugin and tycho
don't integrate as far as I know.

So I am creating release scripts here (to avoid having to manually change versions, tag, etc
on every single release):
  https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/tree/master/script/release
and these require this patch.

      was (Author: ge0ffrey):
    I can't use the release plugin for various reasons [1],
but when I am releasing, I do need to be able to change all my versions from SNAPSHOT to release,
tag and deploy and then from release to SNAPSHOT again.

[1] Here's why I can't use the release plugin:
- Our project has several git repositories with SNAPSHOT dependencies between them: https://github.com/droolsjbpm
(guvnor depends on drools, drools depends on droolsjbpm-knowledge, ...). Having them all in
a single git repo (of 1.2 GB) was unworkable for many reasons, yet for the time being they
do continue to share the same release lifecycle.
- We use tycho for our eclipse plugin (see droolsjbpm-tools). The release plugin and tycho
don't integrate as far as I know.

So I am creating release scripts here (to avoid having to manually change versions, tag, etc
on every single release):
  https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/tree/master/script/release
and these require this patch.
  
> release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion),
so it also supports not suffixing the version with -SNAPSHOT
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-699
>                 URL: https://jira.codehaus.org/browse/MRELEASE-699
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>            Reporter: Geoffrey De Smet
>         Attachments: 0001-MRELEASE-699-release-update-versions-should-support-.patch
>
>
> The documentation
>   http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html
> states "The update-versions goal can use the same properties used by the prepare goal
for specifying the versions to be used."
> That's not true, as releaseVersion is not supported:
>   http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion
> This means, that if you do this:
>   mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0
> that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message