[
https://issues.apache.org/jira/browse/MRELEASE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648239#comment-16648239
]
Carsten Klein edited comment on MRELEASE-897 at 10/12/18 6:08 PM:
------------------------------------------------------------------
[~rfscholte] I have additional requirements, e.g. release tags, e.g. FINAL or
RC1 and so on.
And also a build number that should be included in the version, e.g.
1.0.0-FINAL or 1.0.1-RC1-3233.
But this is mainly for when building applications that then will be put into
docker images and where the docker image will then be tagged using the build
number or when providing release candidates or even beta or alpha releases for
testing.
was (Author: silkentrance):
[~rfscholte] I have additional requirements, e.g. release tags, e.g. FINAL or
RC1 and so on.
And also a build number that should be included in the version, e.g.
1.0.0-FINAL-12345 or 1.0.1-RC1-3233. But this is mainly for when building
applications that then will be put into docker images and where the docker
image will then be tagged using the build number.
> 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)