You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlo de Wolf (JIRA)" <ji...@codehaus.org> on 2010/07/29 11:44:32 UTC

[jira] Created: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Regression: releasing an individual module on a separate release cycle tags the entire project instead
------------------------------------------------------------------------------------------------------

                 Key: MRELEASE-582
                 URL: http://jira.codehaus.org/browse/MRELEASE-582
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
          Components: prepare
    Affects Versions: 2.0, 2.0-beta-9
            Reporter: Carlo de Wolf
            Priority: Critical
         Attachments: dummy.tgz

We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.

See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/

To recreate the bug:
$ svn admin create $HOME/tmp/svn-repo
$ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
$ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
$ (cd dummy; tar zxvf ../dummy.tgz)
Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
$ svn add .
$ svn commit
$ mvn release:prepare
$ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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

        

[jira] Commented: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Posted by "Carlo de Wolf (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230184#action_230184 ] 

Carlo de Wolf commented on MRELEASE-582:
----------------------------------------

The mapping between scm and the directory structure isn't working properly. While the pom has dummy/trunk the actual directory is dummy/trunk/build.

> Regression: releasing an individual module on a separate release cycle tags the entire project instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-582
>                 URL: http://jira.codehaus.org/browse/MRELEASE-582
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Carlo de Wolf
>            Priority: Critical
>         Attachments: dummy.tgz
>
>
> We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.
> See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
> And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
> To recreate the bug:
> $ svn admin create $HOME/tmp/svn-repo
> $ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
> $ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
> $ (cd dummy; tar zxvf ../dummy.tgz)
> Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
> $ svn add .
> $ svn commit
> $ mvn release:prepare
> $ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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

        

[jira] Commented: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230261#action_230261 ] 

Brett Porter commented on MRELEASE-582:
---------------------------------------

I think this is the same as MRELEASE-526 at first glance. I'll try to have a look at these issues and get a release out next week.

> Regression: releasing an individual module on a separate release cycle tags the entire project instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-582
>                 URL: http://jira.codehaus.org/browse/MRELEASE-582
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Carlo de Wolf
>            Priority: Critical
>         Attachments: dummy.tgz
>
>
> We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.
> See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
> And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
> To recreate the bug:
> $ svn admin create $HOME/tmp/svn-repo
> $ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
> $ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
> $ (cd dummy; tar zxvf ../dummy.tgz)
> Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
> $ svn add .
> $ svn commit
> $ mvn release:prepare
> $ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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

        

[jira] Updated: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Posted by "Carlo de Wolf (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf updated MRELEASE-582:
-----------------------------------

    Attachment: dummy.tgz

> Regression: releasing an individual module on a separate release cycle tags the entire project instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-582
>                 URL: http://jira.codehaus.org/browse/MRELEASE-582
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Carlo de Wolf
>            Priority: Critical
>         Attachments: dummy.tgz
>
>
> We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.
> See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
> And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
> To recreate the bug:
> $ svn admin create $HOME/tmp/svn-repo
> $ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
> $ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
> $ (cd dummy; tar zxvf ../dummy.tgz)
> Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
> $ svn add .
> $ svn commit
> $ mvn release:prepare
> $ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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

        

[jira] Updated: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRELEASE-582:
----------------------------------

    Fix Version/s: 2.1

> Regression: releasing an individual module on a separate release cycle tags the entire project instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-582
>                 URL: http://jira.codehaus.org/browse/MRELEASE-582
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Carlo de Wolf
>            Priority: Critical
>             Fix For: 2.1
>
>         Attachments: dummy.tgz
>
>
> We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.
> See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
> And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
> To recreate the bug:
> $ svn admin create $HOME/tmp/svn-repo
> $ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
> $ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
> $ (cd dummy; tar zxvf ../dummy.tgz)
> Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
> $ svn add .
> $ svn commit
> $ mvn release:prepare
> $ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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

        

[jira] Closed: (MRELEASE-582) Regression: releasing an individual module on a separate release cycle tags the entire project instead

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRELEASE-582.
---------------------------------

       Resolution: Not A Bug
    Fix Version/s:     (was: 2.1)
         Assignee: Brett Porter

in this example, the developerConnection is not aligned with the checkout. If you add /build to the end of it, it behaves correctly.

> Regression: releasing an individual module on a separate release cycle tags the entire project instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-582
>                 URL: http://jira.codehaus.org/browse/MRELEASE-582
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-9, 2.0
>            Reporter: Carlo de Wolf
>            Assignee: Brett Porter
>            Priority: Critical
>         Attachments: dummy.tgz
>
>
> We have a lot of projects which use individual release cycles for their respective modules. With the introduction of release plugin 2.0-beta-9 it doesn't tag the module anymore, but the whole project, thus breaking this previous working setup.
> See for example: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/
> And a broken tag: http://anonsvn.jboss.org/repos/jbossas/projects/jboss-aspects/tags/jboss-aspects-build-1.0.2/
> To recreate the bug:
> $ svn admin create $HOME/tmp/svn-repo
> $ svn mkdir --parents file:///$HOME/tmp/svn-repo/dummy/tags file:///$HOME/tmp/svn-repo/dummy/trunk
> $ svn co file:///$HOME/tmp/svn-repo/dummy/trunk dummy
> $ (cd dummy; tar zxvf ../dummy.tgz)
> Modify build/pom.xml to substitute $HOME and use a broken version of release plugin.
> $ svn add .
> $ svn commit
> $ mvn release:prepare
> $ svn ls file:///$HOME/dummy/tags/dummy/tags/build-1.0.x

-- 
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