maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Klein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRELEASE-897) support multiple release versions
Date Fri, 12 Oct 2018 18:19:00 GMT

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

Carsten Klein commented on MRELEASE-897:
----------------------------------------

[~rfscholte] Since I already started development on this, what about

https://issues.apache.org/jira/browse/MRELEASE-897?focusedCommentId=16646785&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16646785

This is key as it prevents others from picking up development. Not to mention the rather complex
architecture of the maven-release plugin, which one must get his head around...

The lombok part is not so much a requirement.

> 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)

Mime
View raw message