[
https://issues.apache.org/jira/browse/MRELEASE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648162#comment-16648162
]
Carsten Klein edited comment on MRELEASE-897 at 10/12/18 5:18 PM:
------------------------------------------------------------------
[~rfscholte] I have looked at MRELEASE-362. The scenario described therein is a
rather complicated one and not something everyone would do. As for
MRELEASE-431, I do have a similar requirement, however, this one would allow me
to control the individual fields in a version, say SemVer, and tell the system
to advance individual fields in order to determine the release version or next
snapshot version.
As to controlling the versions of individual modules and their parents, this is
much more complicated, but I think that I have come up with a working solution
that centres around what I call an AnswerDescriptor. The descriptor is
basically a flat map, similar to the release properties that the maven-release
plugin writes, of project ids (groupId:artifactId) that specifies the actions
to be taken on behalf of a possible parent version, the current release version
and the next development version, e.g.
{code:java}
org.example\:parent.release=skip # no release will be
made, latest was 10
org.example\:parent.development=keep # which currently is
11-SNAPSHOT
org.example\:module1.release=major # current was
2.4.5-SNAPSHOT, will be 3.0.0
org.example\:module1.development=patch # will be 3.0.1-SNAPSHOT
org.example\:module1.parent.release=10 # still using the
existing release 10 of the parent
org.example\:module1.parent.development=current # will be auto resolved
from the reactor
org.example\:module1.tag=true # e.g.
org.example:module1/3.0.0
org.example.sub\:sub-parent.release=next # current is
1-SNAPSHOT, will be 1
org.example.sub\:sub-parent.development=next # will be 2-SNAPSHOT
org.example.sub\:sub-parent.parent.release=10 # still using the
existing release 10 of the parent
org.example.sub\:sub-parent.parent.development=current # will be auto resolved
from the reactor
org.example.sub\:sub-parent.tag=true # e.g.
org.example.sub:sub-parent/1
org.example.sub\:module1.release=skip # no release will be
made
org.example.sub\:module1.development=keep # existing version will
be kept
org.example.sub\:module1.parent=current # will be auto resolved
from the reactor{code}
This is quite redundant and could be leveraged by additional options, e.g.
autoTagModules so one can omit the .tag = true flag.
The system will then consult the "AnwerDescriptor" for each projectId and see
what the specific versions for both the module and its referenced parent are.
And when it comes to tagging, the system will then create tags for each module
using a configurable tag naming strategy or something along that line.
As for MRELEASE-362, for this, the scm must be determined from the respective
module and not just from the root project.
was (Author: silkentrance):
[~rfscholte] I have looked at MRELEASE-362. The scenario described therein is a
rather complicated one and not something everyone would do. As for
MRELEASE-431, I do have a similar requirement, however, this one would allow me
to control the individual fields in a version, say SemVer, and tell the system
to advance individual fields in order to determine the release version or next
snapshot version.
As to controlling the versions of individual modules and their parents, this is
much more complicated, but I think that I have come up with a working solution
that centres around what I call an AnswerDescriptor. The descriptor is
basically a flat map, similar to the release properties that the maven-release
plugin writes, of project ids (groupId:artifactId) that specifies the actions
to be taken on behalf of a possible parent version, the current release version
and the next development version, e.g.
{code:java}
org.example\:parent.release=skip # no release will be
made, latest was 10
org.example\:parent.development=keep # which currently is
11-SNAPSHOT
org.example\:module1.release=major # current was
2.4.5-SNAPSHOT, will be 3.0.0
org.example\:module1.development=patch # will be 3.0.1-SNAPSHOT
org.example\:module1.parent.release=10 # still using the
existing release 10 of the parent
org.example\:module1.parent.development=current # still using the
existing release 10 of the parent
org.example\:module1.tag=true # e.g.
org.example:module1/3.0.0
org.example.sub\:sub-parent.release=next # current is
1-SNAPSHOT, will be 1
org.example.sub\:sub-parent.development=next # will be 2-SNAPSHOT
org.example.sub\:sub-parent.parent.release=10 # still using the
existing release 10 of the parent
org.example.sub\:sub-parent.parent.development=current # will be auto resolved
from the reactor
org.example.sub\:sub-parent.tag=true # e.g.
org.example.sub:sub-parent/1
org.example.sub\:module1.release=skip # no release will be
made
org.example.sub\:module1.development=keep # existing version will
be kept
org.example.sub\:module1.parent=current # will be auto resolved
from the reactor{code}
This is quite redundant and could be leveraged by additional options, e.g.
autoTagModules so one can omit the .tag = true flag.
The system will then consult the "AnwerDescriptor" for each projectId and see
what the specific versions for both the module and its referenced parent are.
And when it comes to tagging, the system will then create tags for each module
using a configurable tag naming strategy or something along that line.
As for MRELEASE-362, for this, the scm must be determined from the respective
module and not just from the root project.
> 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)