[Commented] (MRELEASE-897) support multiple release versions

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Commented] (MRELEASE-897) support multiple release versions

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/MRELEASE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646929#comment-16646929 ]

Robert Scholte commented on MRELEASE-897:
-----------------------------------------

[~silkentrance] I'd suggest to first have a look at MRELEASE-431 and  MRELEASE-362. Those are issues I support. I don't think we should implement the initial proposal of this issue, but first have the requirements clear. A sample would be the best start, including expected result.

> support multiple release versions
> ---------------------------------
>
>                 Key: MRELEASE-897
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-897
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Priority: Major
>
> In some project multiple versions are used (tomee release = tomee + openejb releases for instance). It is not always possible to split the project in sub projects and then it is not possible to use maven release plugin. Idea would be to support a whitelist of artifacts (a list of patterns would be great).
> {code}
> <releaseVersions>
>   <releaseVersion>org.superbiz.component:*:1.0.1</releaseVersion>
>   <releaseVersion>org.superbiz.component:*:4.5.8</releaseVersion>
> </releaseVersions>
> {code}
> For instance or even:
> {code}
> <releaseVersions>
>   <releaseVersion>org.superbiz.component:*:@major.@minor.@patch</releaseVersion>
>   <releaseVersion>org.superbiz.component:*:(@major + 3).@minor.@patch</releaseVersion>
> </releaseVersions>
> {code}
> to avoid to change it for each release.
> This of course would imply the CLI to ask for the multiple versions and not only one even when autoSubModules is set to true (it would just group by versions)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)