[jira] Updated: (MRELEASE-241) Need a tagByProject that works like commitByProject

["Ralf Kretzschmar-Auer (JIRA)" <ji...@codehaus.org>]

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

Ralf Kretzschmar-Auer updated MRELEASE-241:
-------------------------------------------

    Attachment: maven-release-2.0-beta-7-cfs.zip
                maven-release-2.0-beta-7-cfs.patch

This is the patch I decribed in my comment.

maven-release-2.0-beta-7-cfs.patch is a patch export from eclipse patch.
maven-release-2.0-beta-7-cfs.zip is an export of my eclipse project

Have fun

Ralf




> Need a tagByProject that works like commitByProject
> ---------------------------------------------------
>
>                 Key: MRELEASE-241
>                 URL: http://jira.codehaus.org/browse/MRELEASE-241
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-6
>            Reporter: Tim McCune
>         Attachments: maven-release-2.0-beta-7-cfs.patch, maven-release-2.0-beta-7-cfs.zip, releaseExample.tar.gz
>
>
> We have kind of an odd project layout because some of our developers only use Eclipse for CVS, which doesn't handle shared poms that are not part of an actual project very well.  As a result, we have a project structure that looks something like this:
> |-- a
> |   `-- z
> |       |-- pom.xml
> |       `-- src
> |           `-- main
> |               `-- java
> |                   `-- Test.java
> `-- poms
>     |-- a
>     |   `-- pom.xml
>     `-- pom.xml
> Where poms/pom.xml is the top-level shared pom, poms/a/pom.xml is its child, and a/z/pom.xml is a child of poms/a/pom.xml.
> We have never got the release:prepare goal to work successfully on this project.  I discovered the commitByProject configuration property, which got us a lot further when I set it to true.  However, now there is a problem with the CVS tag that it creates, because it runs "cvs tag" in the working directory, and only once, instead of once for each project.  We need that tagging to work the same as the committing, where it executes the tag command once for each pom.  I'm attaching a sample project that demonstrates the problem when you run "mvn release:prepare" on it.

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