[
https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291882#comment-291882
]
Frans edited comment on MRELEASE-679 at 2/16/12 4:43 AM:
---------------------------------------------------------
Same issue. Maven-release-plugin:2.0, Subversion, multi-module project with the
parent POM (for inheritance purposes) outside the project tree, but aggregator
POM at the top level of the project tree.
The only "strange" thing about our setup is that we have a company wide parent
pom that the modules in the multi-module project inherit from. The top-level
pom is only an aggregator pom with <module> entries, not a parent pom in the
inheritance sense.
Structure:
{noformat}
top-level-project (has <module> definitions and scm connectionUrl =
scm:svn:https://svn/repository/project/trunk)
|-- module1 (parent = company-wide parent pom)
|-- module2 (parent = company-wide parent pom)
|-- etc.
{noformat}
With this setup, the release:prepare creates the tag in
https://svn/repository/project/tags/project-version (that's correct), but the
contents are the entire contenst of https://svn/repository/project, i.e.:
{noformat}
project-version
|-- branches
|-- tags
|-- trunk
{noformat}
How this is even possible I don't know. Doesn't it tag your working copy? That
doesn't contain trunk, tags, branches!
I tried changing the scm URL to scm:svn:http://svn/repository/project (without
/trunk) but then it gets even worse: the tag is then created in
https://svn/repository/ and contains the entire contents (i.e. all project
directories) of that SVN repository!
Both variations (with and without /trunk) used to work just fine pre-2.0.
Also tried scm:svn:https://svn/repository/project/ (with trailing slash but
without trunk). Same result as just scm:svn:https://svn/repository/project
(without trailing slash).
was (Author: fransflippo):
Same issue. Maven-release-plugin:2.0, Subversion, multi-module project with
the parent POM (for inheritance purposes) outside the project tree, but
aggregator POM at the top level of the project tree.
The only "strange" thing about our setup is that we have a company wide parent
pom that the modules in the multi-module project inherit from. The top-level
pom is only an aggregator pom with <module> entries, not a parent pom in the
inheritance sense.
Structure:
{code}
top-level-project (has <module> definitions and scm connectionUrl =
scm:svn:https://svn/repository/project/trunk)
|-- module1 (parent = company-wide parent pom)
|-- module2 (parent = company-wide parent pom)
|-- etc.
{/code}
With this setup, the release:prepare creates the tag in
https://svn/repository/project/tags/project-version (that's correct), but the
contents are the entire contenst of https://svn/repository/project, i.e.:
{code}
project-version
|-- branches
|-- tags
|-- trunk
{/code}
How this is even possible I don't know. Doesn't it tag your working copy? That
doesn't contain trunk, tags, branches!
I tried changing the scm URL to scm:svn:http://svn/repository/project (without
/trunk) but then it gets even worse: the tag is then created in
https://svn/repository/ and contains the entire contents (i.e. all project
directories) of that SVN repository!
Both variations (with and without /trunk) used to work just fine pre-2.0.
Also tried scm:svn:https://svn/repository/project/ (with trailing slash but
without trunk). Same result as just scm:svn:https://svn/repository/project
(without trailing slash).
> CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/
> instead of project/trunk
> --------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-679
> URL: https://jira.codehaus.org/browse/MRELEASE-679
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Claus Gebert
> Assignee: Brett Porter
> Priority: Critical
>
> We have switched to the release plug-in 2.0 and are using the prepare goal as
> we did before using version 2.0-beta-9. Unfortunately, the tag which is now
> created is copied from the project level, and from the trunk. With version
> 2.0-beta-9, the tag was correctly copied from the trunk.
> With 2.0-beta-9:
> {noformat}
> /project
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- pom.xml
> |-- src/
> {noformat}
> With 2.0:
> {noformat}
> /project
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- 4.0.1/ (<-- copied from trunk
> |-- trunk/
> |-- pom.xml
> |-- src/
> |-- tags/
> |-- branches/
> {noformat}
> Our _pom.xml_ SCM information is declared as follow:
> {noformat}
> <scm>
>
> <developerConnection>scm:svn:svn://host/path/project/trunk</developerConnection>
> </scm>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
