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

["Erik Petzold (JIRA)" <ji...@codehaus.org>]

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

Erik Petzold commented on MRELEASE-241:
---------------------------------------

I also have a directory structure in svn, which I cannnot change. It is a flat project layout, where the projects are living in different svn locations.

{noformat} 
root
 |-folder1
 |     |-trunk
 |     |   |-project1
 |     |   |   |-pom.xml
 |     |   |-submodule1
 |     |   |   |-pom.xml
 |     |-branches
 |     |-tags
 |
 |-folder2
       |-trunk
       |   |-submodule2
       |   |   |-pom.xml
       |   |-submodule3
       |   |   |-pom.xml
       |-branches
       |-tags
{noformat} 

I think thats basically the same like the ohers had.

The Problem is, that the tag for submodule2 and submodule3 is not set correctly, even if the tag base is correct (there is only one tag-"action" in folder1).

For me it is not important if the commitByProject setting is used for this, or if a new setting tagByProject is created. But I need this in an official release, not a selfmade version with the patch.

Will this be solved in the next versions or will this stay the way it is (this ticket is open for a long time until now).
                
> Need a tagByProject that works like commitByProject
> ---------------------------------------------------
>
>                 Key: MRELEASE-241
>                 URL: https://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
>             Fix For: Backlog
>
>         Attachments: AbstractReleasePhase.java, 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira