[
https://jira.codehaus.org/browse/MRELEASE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-413.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> Branch goal should not insert version information for child modules which do
> not already have it
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-413
> URL: https://jira.codehaus.org/browse/MRELEASE-413
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0-beta-8
> Environment: windows
> Reporter: Andrius Kurtinaitis
> Assignee: Brett Porter
> Attachments: pavyzdys.zip
>
>
> When performing a release:branch on a project which have several child
> modules, the branch plugin updates versions in the parent and also all child
> pom.xml files.
> Even in those files having no <version> information, i.e. those inheriting
> the version from the parent.
> IMO branch plugin should leave those pom.xml files versionless and only
> change those pom.xml files that have their own version.
> I attach one such multimodule project. You will have to edit the scm and
> deployment info to try it.
> What is the preferred form of test cases for plugin issues?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
