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

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

I'm only going to respond on the version-part of your request, all others 
require a new Jira issue.
The only thing I see is business-logic to calculate the next version, in other 
words a 
[VersionPolicy|https://maven.apache.org/maven-release/maven-release-api/apidocs/org/apache/maven/shared/release/policy/version/VersionPolicy.html]
 . Your demands are too specific to implement as part of this plugin, however 
you should be able to solve this with your own Version Policy. If you are 
missing information in the VersionPolicyRequest, we could consider to add that.
You can have a look at the [Odd-Even 
Policy|https://maven.apache.org/maven-release/maven-release-policies/maven-release-oddeven-policy/]
 for inspiration.

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

Reply via email to