[jira] Commented: (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:comment-tabpanel&focusedCommentId=171290#action_171290 ] 

Ralf Kretzschmar-Auer commented on MRELEASE-241:
------------------------------------------------

Hello,


I have the same problem at my company. So I wrote a patch which solves the problem. It is based on Version 2.0-beta-7 of the release plugin. The patch supports poms in parallel Repos and also nested.

It works even in complex situations, where you combine several modules from different locations which may have nested modules themselves, such as

+ Main
|   + pom.xml (root)
|   + Module A
|         + pom.xml (Module A)
|
+ Module B
    + pom.xml (Module B)

To enable it, set commitByProject=true and refer to version 2.0-beta-7-cfs in your POM.

By the way: I did not invent new flags for tagging and branching since it did not make sense to me to treat tags and branches not the same way like checkins.

One last note: The patch was tested with a local Subversion installation. So it might not work with other SCMs - but give it a try.


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