You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Caristi, Joe" <jc...@whisolutions.com> on 2011/05/05 22:16:16 UTC
Multi-module release:prepare creates a tag that includes the tags
folder
I am attempting to use the Maven Release plugin with Maven 3.0.3 to release a flat multi-module structure in Subversion. I have the release:prepare goal working well except for one thing. The tagged release includes the tags folder, which is a sibling of the trunk. Does anyone know how to prevent this from happening? I expected only the trunk folder to be in the tag.
Here are the details:
commitByProject=true (set on command line)
autoVersionSubmodules= true (set in release profile in parent-module pom)
SCM settings:
<scm>
<connection>scm:svn:svn://localhost/project/trunk</connection>
<developerConnection>scm:svn:svn://localhost/project/trunk</developerConnection>
<url>scm:svn:svn://localhost/project/trunk</url>
</scm>
My Subversion folder structure looks like this:
project /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
After running release:prepare on the parent-module for version 1.0.1, which sets all my versions properly and creates a tag, I end up with this:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
The first time I tried this, the nested tags folder was empty. On subsequent runs, it contains all the tags from the previous run:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- parent-1.0.2 /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
________________________________
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. If you are not the intended
recipient, please notify WHI Solutions immediately at gc@whisolutions.com,
and destroy all copies of this message and any attachments.
RE: Multi-module release:prepare creates a tag that includes the
tags folder
Posted by "Caristi, Joe" <jc...@whisolutions.com>.
This worked. Thanks!
-----Original Message-----
From: Nord, James [mailto:JNord@nds.com]
Sent: Friday, May 06, 2011 3:57 AM
To: Maven Users List
Subject: RE: Multi-module release:prepare creates a tag that includes the tags folder
Well you scm setting seems to be wrong.
For your parent module it needs to be
<scm>
<connection>scm:svn:svn://localhost/project/trunk/parent/</connection>
<developerConnection>scm:svn:svn://localhost/project/trunk/parent</developerConnection>
<url>scm:svn:svn://localhost/project/trunk/parent</url>
</scm>
Same for all other modules.
-----Original Message-----
From: Caristi, Joe [mailto:jcaristi@whisolutions.com]
Sent: 05 May 2011 21:16
To: users@maven.apache.org
Subject: Multi-module release:prepare creates a tag that includes the tags folder
I am attempting to use the Maven Release plugin with Maven 3.0.3 to release a flat multi-module structure in Subversion. I have the release:prepare goal working well except for one thing. The tagged release includes the tags folder, which is a sibling of the trunk. Does anyone know how to prevent this from happening? I expected only the trunk folder to be in the tag.
Here are the details:
commitByProject=true (set on command line) autoVersionSubmodules= true (set in release profile in parent-module pom)
SCM settings:
<scm>
<connection>scm:svn:svn://localhost/project/trunk</connection>
<developerConnection>scm:svn:svn://localhost/project/trunk</developerConnection>
<url>scm:svn:svn://localhost/project/trunk</url>
</scm>
My Subversion folder structure looks like this:
project /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
After running release:prepare on the parent-module for version 1.0.1, which sets all my versions properly and creates a tag, I end up with this:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
The first time I tried this, the nested tags folder was empty. On subsequent runs, it contains all the tags from the previous run:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- parent-1.0.2 /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
________________________________
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at gc@whisolutions.com, and destroy all copies of this message and any attachments.
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain confidential or privileged information. If you are not the intended
recipient, please notify WHI Solutions immediately at gc@whisolutions.com,
and destroy all copies of this message and any attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Multi-module release:prepare creates a tag that includes the
tags folder
Posted by "Nord, James" <JN...@nds.com>.
Well you scm setting seems to be wrong.
For your parent module it needs to be
<scm>
<connection>scm:svn:svn://localhost/project/trunk/parent/</connection>
<developerConnection>scm:svn:svn://localhost/project/trunk/parent</developerConnection>
<url>scm:svn:svn://localhost/project/trunk/parent</url>
</scm>
Same for all other modules.
-----Original Message-----
From: Caristi, Joe [mailto:jcaristi@whisolutions.com]
Sent: 05 May 2011 21:16
To: users@maven.apache.org
Subject: Multi-module release:prepare creates a tag that includes the tags folder
I am attempting to use the Maven Release plugin with Maven 3.0.3 to release a flat multi-module structure in Subversion. I have the release:prepare goal working well except for one thing. The tagged release includes the tags folder, which is a sibling of the trunk. Does anyone know how to prevent this from happening? I expected only the trunk folder to be in the tag.
Here are the details:
commitByProject=true (set on command line) autoVersionSubmodules= true (set in release profile in parent-module pom)
SCM settings:
<scm>
<connection>scm:svn:svn://localhost/project/trunk</connection>
<developerConnection>scm:svn:svn://localhost/project/trunk</developerConnection>
<url>scm:svn:svn://localhost/project/trunk</url>
</scm>
My Subversion folder structure looks like this:
project /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
After running release:prepare on the parent-module for version 1.0.1, which sets all my versions properly and creates a tag, I end up with this:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
The first time I tried this, the nested tags folder was empty. On subsequent runs, it contains all the tags from the previous run:
project /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- parent-1.0.2 /
+- tags /
+- parent-1.0.1 /
+- tags /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
+- trunk /
+- parent /
+- child1 /
+- child2 /
________________________________
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify WHI Solutions immediately at gc@whisolutions.com, and destroy all copies of this message and any attachments.
**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.
NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org