On Apr 24, 2008, at 10:18 AM, Brian E. Fox wrote:
I was pretty sure it does tag from the working copy?
well.... from a release I did on march 12
New Revision: 636232
URL: http://svn.apache.org/viewvc?rev=636232&view=rev
Log:
[maven-release-plugin] prepare release directory-parent-1.0
Modified:
geronimo/plugins/directory/branches/1.0/directory/pom.xml
geronimo/plugins/directory/branches/1.0/geronimo-directory-server/
pom.xml
geronimo/plugins/directory/branches/1.0/geronimo-directory/pom.xml
geronimo/plugins/directory/branches/1.0/pom.xml
Modified: geronimo/plugins/directory/branches/1.0/directory/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/plugins/directory/branches/1.0/directory/pom.xml?rev=636232&r1=636231&r2=636232&view=diff
=
=
=
=
=
=
========================================================================
--- geronimo/plugins/directory/branches/1.0/directory/pom.xml (original)
+++ geronimo/plugins/directory/branches/1.0/directory/pom.xml Wed Mar
12 00:23:14 2008
@@ -25,7 +25,7 @@
<parent>
<groupId>org.apache.geronimo.plugins</groupId>
<artifactId>directory-parent</artifactId>
- <version>1.0-SNAPSHOT</version>
+ <version>1.0</version>
<relativePath>../pom.xml</relativePath>
</parent>
..................................
New Revision: 636234
URL: http://svn.apache.org/viewvc?rev=636234&view=rev
Log:
[maven-release-plugin] copy for tag directory-parent-1.0
Added:
geronimo/plugins/directory/tags/directory-parent-1.0/
- copied from r635397, geronimo/plugins/directory/branches/1.0/
........................................
New Revision: 636235
URL: http://svn.apache.org/viewvc?rev=636235&view=rev
Log:
[maven-release-plugin] prepare for next development iteration
Modified:
geronimo/plugins/directory/branches/1.0/directory/pom.xml
geronimo/plugins/directory/branches/1.0/geronimo-directory-server/
pom.xml
geronimo/plugins/directory/branches/1.0/geronimo-directory/pom.xml
geronimo/plugins/directory/branches/1.0/pom.xml
Modified: geronimo/plugins/directory/branches/1.0/directory/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/plugins/directory/branches/1.0/directory/pom.xml?rev=636235&r1=636234&r2=636235&view=diff
=
=
=
=
=
=
========================================================================
--- geronimo/plugins/directory/branches/1.0/directory/pom.xml (original)
+++ geronimo/plugins/directory/branches/1.0/directory/pom.xml Wed Mar
12 00:26:14 2008
@@ -25,7 +25,7 @@
<parent>
<groupId>org.apache.geronimo.plugins</groupId>
<artifactId>directory-parent</artifactId>
- <version>1.0</version>
+ <version>1.0.1-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
.....................................
which looks to me like the release plugin is following the process I
outlined.
thanks
david jencks
.......
-----Original Message-----
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 24, 2008 1:07 PM
To: Maven Developers List
Subject: Where should release plugin copy from?
In my experience the release plugin currently works like this:
1. modifies working copy poms to release version
2. commits poms
3. does a repo-repo copy to the new tag
4. updates working copy poms to the new version
5. commits new-version poms.
Some projects (activemq) have a versioning scheme whereby branches,
say 4.1, are kept at version 4.1-SNAPSHOT forever and releases, such
as 4.1.1, 4.1.2, ..., are tagged directly off of the branch. The
current release plugin process thus results in 2 commits to all the
poms in the branch that modify the versions, then modify them back to
their original values.
This creates a fair amount of noise in the scm lists.
Would it be possible for the release plugin to do the following?
1. modify working copy poms to release version
2. do a working copy to repo copy for the new tag
3. adjust the working copy poms to the new version, or revert if the
new version is the same as the old version
4. commit the working copy poms if there is a new version.
Is this process svn specific? If so could it be provided as an
option?
thanks
david jencks
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
