[
https://jira.codehaus.org/browse/MRELEASE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Romain Manni-Bucau updated MRELEASE-897:
----------------------------------------
Description:
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)
was:
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).
<releaseVersions>
<releaseVersion>org.superbiz.component:*:1.0.1</releaseVersion>
<releaseVersion>org.superbiz.component:*:4.5.8</releaseVersion>
</releaseVersions>
For instance or even:
<releaseVersions>
<releaseVersion>org.superbiz.component:*:@major.@minor.@patch</releaseVersion>
<releaseVersion>org.superbiz.component:*:(@major +
3).@minor.@patch</releaseVersion>
</releaseVersions>
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)
> support multiple release versions
> ---------------------------------
>
> Key: MRELEASE-897
> URL: https://jira.codehaus.org/browse/MRELEASE-897
> Project: Maven Release Plugin
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
>
> 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
(v6.1.6#6162)
