[Comment Edited] (MRELEASE-897) support multiple release versions

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

[Comment Edited] (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=16646849#comment-16646849 ]

Carsten Klein edited comment on MRELEASE-897 at 10/11/18 6:24 PM:
------------------------------------------------------------------

Are there any objections against introducing lombok? That way, the release descriptor, the builder thingy and everything else could be simplified, removing a lot of getter/setter code and so on.

I know, that there are a lot of resentments towards lombok, but as far as I can tell, it is working just fine and the generated code is working as expected.

Of course, the missing hashCode() and equals() implementations on the core maven model would prevent such use, namely the Scm model class does not implement this.


was (Author: silkentrance):
Are there any objections against introducing lombok? That way, the release descriptor, the builder thingy and everything else could be simplified, removing a lot of getter/setter code and so on.

I know, that there are a lot of resentments towards lombok, but as far as I can tell, it is working just fine and the generated code is working as expected.

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