[ 
https://jira.codehaus.org/browse/MRELEASE-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300233#comment-300233
 ] 

Robert Scholte commented on MRELEASE-714:
-----------------------------------------

Looks related to MRELEASE-760 and should be fixed by now. Can you confirm this?

About your off topic issue: Looks related to MRELEASE-241.
If child1 and child2 are subfolders of parent then you don't want to have 
version-numbers in the module names. 
You must be able to check out the code by tag and run {{mvn install}}.
To find child1-1.0.0 you always have to find tags/parent-1.0.0 first, so the 
information will be redundant.
                
> Prevent snapshot version bumping does not seem to work
> ------------------------------------------------------
>
>                 Key: MRELEASE-714
>                 URL: https://jira.codehaus.org/browse/MRELEASE-714
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>            Reporter: Paul S
>
> I want to use the release plugin within our company, and I want to create a 
> tags for multi-module projects, such as the following example:
> {noformat}
> tags/parent-1.0.0
> - child1  (1.0.0)
> - child2  (1.0.0)
> {noformat}
> When I do "{{release:prepare}}", snapshots with an increased version are 
> created and committed for every parent/child module, so:
> {{parent-1.0.0-SNAPSHOT, child1-1.0.0-SNAPSHOT, child2-1.0.0-SNAPSHOT}}
> becomes:
> {{parent-1.0.1-SNAPSHOT, child1-1.0.1-SNAPSHOT, child2-1.0.1-SNAPSHOT}}
> However, when I create a release I don't want to automatically create 
> snapshot versions for every child module, so I'd like to bump the version 
> number to 1.0.1-SNAPSHOT manually. Sometimes we create a new release in which 
> for instance 3 of the 10 child modules have actually been updated, so we want 
> to just set those 3 version numbers to an increased SNAPSHOT version. I tried 
> accomplishing this by setting the following properties to false:
> {code:xml}
> <updateWorkingCopyVersions>false</updateWorkingCopyVersions>
> <updateDependencies>false</updateDependencies>
> {code}
> However, whatever I try, it doesn't work. The 1.0.0-SNAPSHOT versions keep 
> getting bumped to 1.0.1-SNAPSHOT.
> Furthermore, a little off topic, but is it possible to have version numbers 
> created for sub modules? E.g.: 
> {noformat}
> tags/parent-1.0.0
> - child1-1.0.0
> - child2-1.0.0)
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to