maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MRELEASE-241) Need a tagByProject that works like commitByProject
Date Fri, 05 Apr 2013 19:16:54 GMT

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

Robert Scholte commented on MRELEASE-241:
-----------------------------------------

Apart from the fact that some SCM-systems don't support tagging of a specific folder, in a
hierarchical structure a tagByProject would tag too much (don't think it is possible to exclude
the module-folders). In a (oldfashion) flat structure I can imagine the wish. A few weeks
ago Stephen Connolly started a thread about what he called "local aggregator". 
His proposal starts with listing release-roots, a next step would be to actually do a multi
project release in one go.
Read http://maven.markmail.org/thread/ntwc537akvsjsegq to get an impression of stategies,
concerns and complexity.
                
> 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:
> {noformat}
> |-- a
> |   `-- z
> |       |-- pom.xml
> |       `-- src
> |           `-- main
> |               `-- java
> |                   `-- Test.java
> `-- poms
>     |-- a
>     |   `-- pom.xml
>     `-- pom.xml
> {noformat}
> 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

Mime
View raw message