svn commit: r1214999 - /commons/proper/commons-parent/trunk/pom.xml

[se...@apache.org]

Author: sebb
Date: Fri Dec 16 00:04:58 2011
New Revision: 1214999

URL: http://svn.apache.org/viewvc?rev=1214999&view=rev
Log:
Allow override of SVN provider in buildnumber maven plugin

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

Modified: commons/proper/commons-parent/trunk/pom.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?rev=1214999&r1=1214998&r2=1214999&view=diff
==============================================================================
--- commons/proper/commons-parent/trunk/pom.xml (original)
+++ commons/proper/commons-parent/trunk/pom.xml Fri Dec 16 00:04:58 2011
@@ -446,7 +446,7 @@
           <revisionOnScmFailure>??????</revisionOnScmFailure>
           <!-- svnjava works even if an svn command-line client is not on the path -->
           <providerImplementations>
-            <svn>javasvn</svn>
+            <svn>${maven.buildNumber.svnProvider}</svn>
           </providerImplementations>
         </configuration>
       </plugin>
@@ -1064,6 +1064,12 @@
     <!-- build meta inf -->
     <maven.build.timestamp.format>yyyy-MM-dd HH:mm:ssZ</maven.build.timestamp.format>
     <implementation.build>${scmBranch}@r${buildNumber}; ${maven.build.timestamp}</implementation.build>
+    
+    <!-- 
+        make the maven build svn application overrideable
+        If javasvn does not work, try using -Dmaven.buildNumber.svnProvider=svn 
+    -->
+    <maven.buildNumber.svnProvider>javasvn</maven.buildNumber.svnProvider>
 
     <!-- Allow Clirr severity to be overriden by the command-line option -DminSeverity=level -->
     <minSeverity>info</minSeverity>