You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org> on 2010/02/22 12:02:55 UTC
[jira] Created: (MRELEASE-526) release:prepare 2.0 goal tags at the
wrong level, tagging project/ instead of project/trunk
release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
-------------------------------------------------------------------------------------------
Key: MRELEASE-526
URL: http://jira.codehaus.org/browse/MRELEASE-526
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0
Environment: Maven 2.2.1
Reporter: Damien Coraboeuf
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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Todd Thiessen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214550#action_214550 ]
Todd Thiessen commented on MRELEASE-526:
----------------------------------------
I just tried upgrading to 2.0 and found the same thing. Show stopper bug for us and have to revert back to beta-9.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-526) release:prepare 2.0
goal tags at the wrong level, tagging project/ instead of project/trunk
Posted by "Sebastian Annies (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219055#action_219055 ]
Sebastian Annies edited comment on MRELEASE-526 at 4/27/10 2:27 AM:
--------------------------------------------------------------------
Same for git. It's a blocker since. 2.0 is useless for git users as far as I can see.
Is this related to MRELEASE-546? Is it fixed by change 933531?
was (Author: sannies):
Same for git. It's a blocker since. 2.0 is useless for git users as far as I can see.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "James Blewitt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221490#action_221490 ]
James Blewitt commented on MRELEASE-526:
----------------------------------------
There is a bug in the way the release plugin calculates the path to use as the tag base directory. We have also had this problem and have modified the release plugin (locally) to solve the problem. The cause of the problem is a little bit tricky to explain, but I'll try my best:
*The trigger for this problem is as follows:*
Suppose we have projects A, B, C and D
{noformat}
A
|-B
|-C
\-D
{noformat}
* Projects B, C and D are all in the <modules> list of project A.
* Projects C and D have A as parent.
* Project B has no parent (or a parent other than A).
Because project B does not depend on A, it may appear before A in the reactor build order. This can easily be tested for by looking at the "Reactor build order" that appears when you do "release:prepare". Usually you would expect project A to be the first entry in this list.
*The program fault:*
The faulty code is in the "maven-release-manager" (a module used by the "maven-release-helper").
The file *org.apache.maven.shared.release.util.ReleaseUtil* in method *getCommonBasedir* is where the error lies.
This method should find the base directory shared by all projects in the reactor. This directory will be used as the base directory from which to perform the tag.
It works by looking at all paths for all projects in the reactor and finding the "prefix" that is common to all path strings.
E.g.
c:/path/to/projectA-1.5
c:/path/to/projectB-2.1
c:/path/to/projectC-1.0
The "common prefix" would be "c:/path/to/project". Because this is not a valid path (there is no "project" directory) it cuts off the string from the last "/" leaving "c:/path/to".
Returning to our example above: we would have the following input for this method:
c:/path/to/projectA
c:/path/to/projectA/projectB
c:/path/to/projectA/projectC
c:/path/to/projectA/projectD
Because the method needs to return "c:/path/to/projectA" (and not "c/path/to") as the base directory, the algorithm adds an additional "/" to the end of paths to ensure that the "common suffix" is a valid path (i.e. doesn't get shortened as in the first example).
This works fine, but as soon as the project order looks like the following it doesn't work correctly:
c:/path/to/projectA/projectB
c:/path/to/projectA
c:/path/to/projectA/projectC
c:/path/to/projectA/projectD
This is exactly the sequence that you get when B doesn't have A for a parent (the trigger condition).
The algorithm fails to append "/" to the second path and the returned path is "c:/path/to" instead of "c:/path/to/projectA" and this is then used as the base directory for the tag. This is why the generated tag is one level too high in the directory tree.
*The fix:*
This method at the moment is as follows:
{noformat}
public static String getCommonBasedir( List reactorProjects, char separator )
{
String basedir = null;
for ( Iterator i = reactorProjects.iterator(); i.hasNext(); )
{
MavenProject p = (MavenProject) i.next();
// we can only normalize paths with /
String dir = FileUtils.normalize( p.getBasedir().getPath().replace( '\\', '/' ) );
if ( basedir == null )
{
basedir = dir;
}
else
{
// always end in / so that we know what is a path and what is a partial directory name in the next call
if ( !basedir.endsWith( "/" ) )
{
basedir = basedir + "/";
}
basedir = StringUtils.getCommonPrefix( new String[]{dir, basedir} );
if ( !basedir.endsWith( "/" ) )
{
basedir = basedir.substring( 0, basedir.lastIndexOf( "/" ) );
}
}
}
if ( basedir != null )
{
if ( basedir.endsWith( "/" ) && basedir.length() > 1 )
{
basedir = basedir.substring( 0, basedir.length() - 1 );
}
basedir = basedir.replace( '/', separator );
}
return basedir;
}
{noformat}
It can be changed to the following, which correctly appends "/" to the end of both "basedir" AND "dir", which solves the problem.
{noformat}
public static String getCommonBasedir(List reactorProjects, char separator) {
String basedir = null;
for (Iterator i = reactorProjects.iterator(); i.hasNext();) {
MavenProject p = (MavenProject) i.next();
// we can only normalize paths with /
String dir = FileUtils.normalize(p.getBasedir().getPath().replace('\\', '/'));
// always end in / so that we know what is a path and what is a partial directory name in the next call
if (!dir.endsWith("/")) {
dir = dir + "/";
}
if (basedir == null) {
basedir = dir;
} else {
basedir = StringUtils.getCommonPrefix(new String[] { dir, basedir });
if (!basedir.endsWith("/")) {
basedir = basedir.substring(0, basedir.lastIndexOf("/"));
}
}
}
if (basedir != null) {
if (basedir.endsWith("/") && basedir.length() > 1) {
basedir = basedir.substring(0, basedir.length() - 1);
}
basedir = basedir.replace('/', separator);
}
return basedir;
}
{noformat}
Sorry for the long post!
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Samuel Santos (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212350#action_212350 ]
Samuel Santos commented on MRELEASE-526:
----------------------------------------
Same thing here. But even downgrading the plugin version won't do it.
Each time I run {{mvn release:prepare}} it copies the trunk folder into the new tag (as can be seen here: http://maven-minify-plugin.googlecode.com/svn/tags/maven-minify-plugin-1.2).
Can't find anything wrong in my POM - http://maven-minify-plugin.googlecode.com/svn/trunk/pom.xml.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.0.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211048#action_211048 ]
Damien Coraboeuf commented on MRELEASE-526:
-------------------------------------------
I will prepare a small project and try to reproduce the problem. I will just have to obfuscate the URLs.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.0.1
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Tim Collins (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214833#action_214833 ]
Tim Collins commented on MRELEASE-526:
--------------------------------------
Same issue with mercurial, tagging fails because the working directory is one level too high.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-526) release:prepare 2.0 goal tags at the
wrong level, tagging project/ instead of project/trunk
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRELEASE-526.
---------------------------------
Resolution: Duplicate
Fix Version/s: (was: 2.1)
Assignee: Brett Porter
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Samuel Santos (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269296#action_269296 ]
Samuel Santos commented on MRELEASE-526:
----------------------------------------
The new issue is MRELEASE-679.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Claus Gebert (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265836#action_265836 ]
Claus Gebert commented on MRELEASE-526:
---------------------------------------
I have to agree with James Bowkett. We did not have this problem with Maven 2.2.1, which comes with the v2.0-beta-8 of the release plugin. Switching to Maven 3.0.3 (i.e. to v2.0 of the plugin) leads to this problem. As far as I can tell this is clearly not a duplicate to MRELEASE-546. Can this issue be changed to another status than closed? Or should I create a new issue? And what about the fix proposed by James Blewitt?
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Yves Langisch (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269282#action_269282 ]
Yves Langisch commented on MRELEASE-526:
----------------------------------------
Where is the new issue? I have the same prolem with Maven 3.0.3 and the plugin versions 2.0 and 2.1.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211041#action_211041 ]
Damien Coraboeuf commented on MRELEASE-526:
-------------------------------------------
The structure is indeed looking like:
{noformat}
/project
|-- pom.xml
| |--> <scm>
| |--> <developerConnection>
| |--> </scm>
|-- moduleA/
|-- moduleB/
{noformat}
I will test with <connection> being declared as well.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-526) release:prepare 2.0
goal tags at the wrong level, tagging project/ instead of project/trunk
Posted by "Samuel Santos (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212350#action_212350 ]
Samuel Santos edited comment on MRELEASE-526 at 3/19/10 8:07 PM:
-----------------------------------------------------------------
Same thing here. But even downgrading the plugin version won't do it.
Each time I run {{mvn release:prepare}} it copies the trunk folder into the new tag.
was (Author: samaxes):
Same thing here. But even downgrading the plugin version won't do it.
Each time I run {{mvn release:prepare}} it copies the trunk folder into the new tag (as can be seen here: http://maven-minify-plugin.googlecode.com/svn/tags/maven-minify-plugin-1.2).
Can't find anything wrong in my POM - http://maven-minify-plugin.googlecode.com/svn/trunk/pom.xml.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Petr Kozelka (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232662#action_232662 ]
Petr Kozelka commented on MRELEASE-526:
---------------------------------------
same problem here; I observe it only on multimodule projects, and not strictly always - which seems to be confirming the explanation above
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-526) release:prepare 2.0 goal tags at the
wrong level, tagging project/ instead of project/trunk
Posted by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Damien Coraboeuf updated MRELEASE-526:
--------------------------------------
Attachment: export.zip
I've created a sample project that allowed me reproduce the problem.
The interesting thing is that I _cannot_ reproduce the problem if I run the release:prepare command from my environment, but only when I run this build from Hudson. So maybe it's linked somehow with Hudson.
Here is the actual build step that is called:
{noformat}
Executing Maven: -B -f /opt/hudson/jobs/MRelease-526/workspace/./pom.xml -B clean install release:clean release:prepare -DautoVersionSubmodules=true -DreleaseVersion=0.7.0 -DdevelopmentVersion=0.8.0-SNAPSHOT -Dtag=0.7.0 -DpreparationGoals=clean install
{noformat}
And here is the output about the tagging part:
{noformat}
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace/. && svn --non-interactive commit --file /tmp/maven-scm-1832850485.commit --targets /tmp/maven-scm-1057416757279716410-targets
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace/.
[INFO] Tagging release with the label 0.7.0...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace && svn --non-interactive copy --file /tmp/maven-scm-1386345960.commit --revision 39 svn://192.168.37.24/maven/mrelease526 svn://192.168.37.24/maven/mrelease526/tags/0.7.0
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace
[INFO] Transforming 'Unnamed - org.apache.maven:mrelease526:pom:0.7.0-SNAPSHOT'...
[INFO] Transforming 'Unnamed - org.apache.maven:moduleA:jar:0.7.0-SNAPSHOT'...
[INFO] Transforming 'Unnamed - org.apache.maven:moduleB:jar:0.7.0-SNAPSHOT'...
[INFO] Not removing release POMs
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /opt/hudson/jobs/MRelease-526/workspace/. && svn --non-interactive commit --file /tmp/maven-scm-1044767202.commit --targets /tmp/maven-scm-4622755560941691278-targets
[INFO] Working directory: /opt/hudson/jobs/MRelease-526/workspace/.
[INFO] Release preparation complete.
{noformat}
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.0.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-526) release:prepare 2.0 goal tags at the
wrong level, tagging project/ instead of project/trunk
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRELEASE-526:
----------------------------------
Fix Version/s: 2.0.1
Thanks - I'll put this in the list for the next version.
Are you able to reproduce this with a small sample project that you can share with us to make it easier to reproduce?
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.0.1
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211039#action_211039 ]
Brett Porter commented on MRELEASE-526:
---------------------------------------
there were changes to locate the root in non-standard layouts - do you have a parent in svn://host/path/project/somewhere-else ? Do you have <connection> set anywhere?
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211042#action_211042 ]
Brett Porter commented on MRELEASE-526:
---------------------------------------
if /project/trunk is the top level (Assuming that's what you meant here), that's the expected layout. If you have something 'above' trunk or in a directory at the same level as it, that might be the problem.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211044#action_211044 ]
Damien Coraboeuf commented on MRELEASE-526:
-------------------------------------------
The project layout is fairly standard (I forgot to indicate the full trunk/tags structure in my snippet above):
{noformat}
/project
/trunk
|-- pom.xml
| |--> <scm>
| |--> <developerConnection>
| |--> </scm>
|-- moduleA/
|-- moduleB/
/tags
/branches
{noformat}
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Damien Coraboeuf (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211045#action_211045 ]
Damien Coraboeuf commented on MRELEASE-526:
-------------------------------------------
So:
* I added the <connection> URL in the parent POM (same as developer connection actually)
* I switched back to the maven-release-plugin 2.0 version (in the plugin management section)
The tag is created from the project/
When I use the maven-release-plugin 2.0.9 version, the tag is created from the trunk.
Here is an extract of the parent POM about the release plug-in configuration:
{noformat}
<build>
<pluginManagement>
...
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0</version>
</plugin>
</plugins>
...
</pluginManagement>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<remoteTagging>true</remoteTagging>
</configuration>
</plugin>
...
</plugins>
</build>
{noformat}
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "James Bowkett (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248905#action_248905 ]
James Bowkett commented on MRELEASE-526:
----------------------------------------
I still have this problem and I just tried release plugin 2.1. If in v2.1 of the plugin I have the fix for issue MRELEASE546, then I believe this isn't _exactly_ the same bug, as I'm still seeing the behaviour others have outlined above, and I have a multi-module project with inheritance also.
This originally all worked fine in v2.0-beta-8 of the plugin
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "John Crim (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212232#action_212232 ]
John Crim commented on MRELEASE-526:
------------------------------------
I'm seeing the exact same behavior. This is a real problem, so need to revert to 2.0-beta-9.
To simplify the problem description further, if I run:
{noformat}
mvn org.apache.maven.plugins:maven-release-plugin:2.0-beta-8:prepare -DdryRun -Dresume=false
{noformat}
I see:
{noformat}
...
[INFO] Full run would be tagging C:\code\common\projectA\trunk with label: 'projectA-1.0'
{noformat}
If I run:
{noformat}
mvn org.apache.maven.plugins:maven-release-plugin:2.0:prepare -DdryRun -Dresume=false
{noformat}
I see:
{noformat}
...
[INFO] Full run would be tagging working copy C:\code\common\projectA with label: 'projectA-1.0'
{noformat}
2.0-beta-9 gives me the same result as 2.0-beta-8.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.0.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265839#action_265839 ]
Dennis Lundberg commented on MRELEASE-526:
------------------------------------------
Claus,
Please open a new issue.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Assignee: Brett Porter
> Priority: Critical
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at
the wrong level, tagging project/ instead of project/trunk
Posted by "Sebastian Annies (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219055#action_219055 ]
Sebastian Annies commented on MRELEASE-526:
-------------------------------------------
Same for git. It's a blocker since. 2.0 is useless for git users as far as I can see.
> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk
> -------------------------------------------------------------------------------------------
>
> Key: MRELEASE-526
> URL: http://jira.codehaus.org/browse/MRELEASE-526
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0
> Environment: Maven 2.2.1
> Reporter: Damien Coraboeuf
> Priority: Critical
> Fix For: 2.1
>
> Attachments: export.zip
>
>
> 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira