On 11/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: dennisl
Date: Sun Nov 12 12:46:01 2006
New Revision: 474040

URL: http://svn.apache.org/viewvc?view=rev&rev=474040
Log:
[maven-release-plugin] prepare for next development iteration

Modified:
    jakarta/commons/proper/commons-parent/trunk/pom.xml

<snip/>

   <scm>
-    
<connection>scm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-parent/tags/commons-parent-1</connection>
-    
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-parent/tags/commons-parent-1</developerConnection>
-    
<url>http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/tags/commons-parent-1</url>
+    
<connection>scm:svn:http://svn.apache.org/repos/asf/jakarta/commons/proper/commons-parent/trunk</connection>
+    
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-parent/trunk</developerConnection>
+    
<url>http://svn.apache.org/viewvc/jakarta/commons/proper/commons-parent/trunk</url>
   </scm>

<snap/>

Should we be changing POM SCM bits in a release tag? i.e. are the SCM
bits project-specific or release-specific meta-data?

I haven't changed them for recent releases I've cut (I don't think
many of us do), so would be nice to know.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to