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] [Comment Edited] (MRELEASE-897) support multiple release versions
Date Fri, 12 Oct 2018 18:03:00 GMT

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

Carsten Klein edited comment on MRELEASE-897 at 10/12/18 6:02 PM:
------------------------------------------------------------------

[~rfscholte] As for naming the target versions, I came up with an enum called VersionIndicator,
which is basically just
{code:java}
public enum VersionIndicator {

  SKIP, NEXT, CURRENT, MAJOR, MINOR, PATCH, CUSTOM, LATEST;
}{code}
Where
 * SKIP specifies that no change in the version is to take place, e.g. release = skip
 * NEXT specifies that the next version, derived from the current release or development version,
will be taken, e.g. development = next.
 * CURRENT specifies that the version must be looked up from the reactor, e.g. parent.development
= current.
 * MAJOR specifies that the next release version is a major release, e.g. release = major.
 * MINOR specifies that the next release version is a minor release, e.g. release = minor.
 * PATCH specifies that the next release version is a patch release, e.g. development = patch.
 * CUSTOM specifies that the user provided a custom version number, e.g. release = 10.0.0
or parent.release = 5.9.4-FINAL.
 * LATEST specifies that the latest release version must be looked up from either the reactor
or the maven repositories, e.g. parent.release = latest.

 


was (Author: silkentrance):
[~rfscholte] As for naming the target versions, I came up with an enum called VersionIndicator,
which is basically just
{code:java}
public enum VersionIndicator {

  SKIP, NEXT, CURRENT, MAJOR, MINOR, PATCH, CUSTOM, LATEST;
}{code}
Where
 * SKIP specifies that no change in the version is to take place, e.g. release = skip
 * NEXT specifies that the next version, derived from the current release or development version,
will be taken, e.g. development = next.
 * CURRENT specifies that the version must be looked up from the reactor, e.g. parent.development
= current.
 * MAJOR specifies that the next release version is a major release, e.g. release = major.
 * MINOR specifies that the next release version is a minor release, e.g. release = minor.
 * PATCH specifies that the next release version is a patch release, e.g. development = patch.
 * CUSTOM specifies that the user provided a custom version number, e.g. release = 10.0.0.
 * LATEST specifies that the latest release version must be looked up from either the reactor
or the maven repositories, e.g. parent.release = latest.

 

> 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