Carsten Klein commented on MRELEASE-897:
I am currently looking into this feature as I need it both for my personal projects and for work.
Looking at the code, I have a few questions:
# I need to make changes to the ReleaseDescriptor API. Currently, the release descriptor is generated from some modello model.
# Similar so for the ReleaseStageVersions class, which is also simple enough to implement it directly.
Do you have and objections in removing this extra dependency (modello code generation for two classes) and implement both directly?
Must the name ModelloReleaseDescriptor be preserved or can it be renamed to just DefaultReleaseDescriptor?
There are also two helper classes, namely ReleaseDescriptorXpp3Reader and ReleaseDescriptorXpp3Writer, which, as far as I can tell,
are never used by the maven release plugin. Can these two be removed?
> 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).
> For instance or even:
> <releaseVersion>org.superbiz.component:*:(@major + 3).@minor.@patch</releaseVersion>
> 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