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

Carsten Klein edited comment on MRELEASE-897 at 10/12/18 5:45 PM:
------------------------------------------------------------------

[~rfscholte] instead of anwer descriptor one could also name this a 
ReleasePlan. This could also be provided via, e.g., the _release:plan_ goal. 
This will then output a template using standard versions. The release plan 
would then be edited by the user and _release:prepare_ would automatically pick 
it up.

As for automation in a CI environment, this is rather tricky. While one could 
pass in a predefined ReleasePlan as a parameter to the build, this would 
require manual intervention of the, say, ReleaseManager. Alternatively, the 
user would have to provide a configuration via the POM. before each automated 
release, which adds additional complexity to the overall process since the POM 
must be updated prior to that a release branch is committed and from where the 
release will be build from.

CI: The _release:prepare_ goal could also look for a release-plan.properties 
file in the working copy, which would have been committed and pushed into the 
release branch. This could then be removed by the release plugin before that 
the release was finalised, committed, tagged and finally merged into master. 
For documentation purposes, the release-plan.properties file could also be kept 
in the repository.


was (Author: silkentrance):
[~rfscholte] instead of anwer descriptor one could also name this a 
ReleasePlan. This could also be provided via, e.g., the _release:plan_ goal. 
This will then output a template using standard versions. The release plan 
would then be edited by the user and _release:prepare_ would automatically pick 
it up.

As for automation in a CI environment, this is rather tricky. While one could 
pass in a predefined ReleasePlan as a parameter to the build, this would 
require manual intervention of the, say, ReleaseManager. Alternatively, the 
user would have to provide a configuration via the POM. before each automated 
release, which adds additional complexity to the overall process since the POM 
must be updated prior to that a release branch is committed and from where the 
release will be build from.

CI: The _release:prepare_ goal could also look for a release-plan.properties 
file in the working copy, which would have been committed and pushed into the 
release branch. This would then be removed from the release plugin before that 
the release was finalised, committed, tagged and finally merged into master. 
For documentation purposes, the release-plan.properties file could also be kept 
in the repository.

> 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