[jira] Closed: (MRELEASE-413) Branch goal should not insert version information for child modules which do not already have it

["Brett Porter (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRELEASE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRELEASE-413.
---------------------------------

    Resolution: Won't Fix
      Assignee: Brett Porter

correct behaviour, and you can use autoVersionSubModules to not worry about typos

> Branch goal should not insert version information for child modules which do not already have it
> ------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-413
>                 URL: http://jira.codehaus.org/browse/MRELEASE-413
>             Project: Maven 2.x 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira