Hi Mick

The error message sais, that you have no subversion client installed.
The plugin's default settings tries to use the subversion revision as your
buildnumber and therefore requires the client to be present. You can either
- install subversion client (only makes sense if you are using subversion in
your project of course...)
- use -Dmaven.buildNumber.skipUpdate=true -Dmaven.buildNumber.skipCheck=true
when starting mvn
(like: mvn package -Dmaven.buildNumber.skipUpdate=true
-Dmaven.buildNumber.skipCheck=true) AND
use the "format" feature of the plugin which will create increasing numbers
instead of svn revision numbers.
I didn't test the second point though...

Details are at:
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html

Your format would look something like:

<build>
  <plugins>
    <plugin>
      <groupId>org.codehaus.mojo</groupId>
      <artifactId>maven-buildnumber-plugin</artifactId>
      <version>0.9.2-SNAPSHOT</version>
      <configuration>
        <format>{0,number}.{1,number}.{2,number}</format>
        <items>
          <item>buildNumber0</item>
          <item>buildNumber1</item>
          <item>buildNumber2</item>
        </items>
      </configuration>
      <executions>
        <execution>
          <goals>
            <goal>create</goal>
          </goals>
        </execution>
      </executions>
    </plugin>
</build>

Regards,
Kay



Mick Knutson-4 wrote:
> 
> Why am I getting svn errors when I downloaded this module to compile
> locally:
> 
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.codehaus.mojo.buildNumber.TestCreateBuildNumber
> process = [EMAIL PROTECTED]
> Provider message:
> The svn command failed.
> Command output:
> 'svn' is not recognized as an internal or external command,
> operable program or batch file.
> 
> org.apache.maven.plugin.MojoExecutionException: Cannot get the revision
> information from the scm repository :
> Error!
>         at org.codehaus.mojo.buildNumber.BuildNumberMojo.getRevision(
> BuildNumberMojo.java:421)
>         at org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(
> BuildNumberMojo.java:310)
>         at
> org.codehaus.mojo.buildNumber.TestCreateBuildNumber.testSvnRevision(
> TestCreateBuildNumber.java:85)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>         at java.lang.reflect.Method.invoke(Unknown Source)
>         at junit.framework.TestCase.runTest(TestCase.java:154)
>         at junit.framework.TestCase.runBare(TestCase.java:127)
>         at junit.framework.TestResult$1.protect(TestResult.java:106)
>         at junit.framework.TestResult.runProtected(TestResult.java:124)
>         at junit.framework.TestResult.run(TestResult.java:109)
>         at junit.framework.TestCase.run(TestCase.java:118)
>         at junit.framework.TestSuite.runTest(TestSuite.java:208)
>         at junit.framework.TestSuite.run(TestSuite.java:203)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>         at java.lang.reflect.Method.invoke(Unknown Source)
>         at org.apache.maven.surefire.junit.JUnitTestSet.execute(
> JUnitTestSet.java:210)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
> AbstractDirectoryTestSuite.java:135)
>         at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
> AbstractDirectoryTestSuite.java:122)
>         at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>         at java.lang.reflect.Method.invoke(Unknown Source)
>         at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
> SurefireBooter.java:225)
>         at org.apache.maven.surefire.booter.SurefireBooter.main(
> SurefireBooter.java:747)
> Caused by: org.apache.maven.scm.ScmException: Error!
>         at org.codehaus.mojo.buildNumber.BuildNumberMojo.checkResult(
> BuildNumberMojo.java:513)
>         at org.codehaus.mojo.buildNumber.BuildNumberMojo.getRevision(
> BuildNumberMojo.java:415)
>         ... 28 more
> rev = At 3:22:24 PM on Nov 1, 2006, there was a disturbance in the Force
> on
> planet 7.
> rev = 3.3.3
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.61 sec
> <<<
> FAILURE!
> 
> Results :
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0
> 
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.BuildFailureException: There are test failures.
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:555)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
> (DefaultLifecycleExecutor.java:475)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
> DefaultLifecycleExecutor.java:454)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
> (DefaultLifecycleExecutor.java:306)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
> DefaultLifecycleExecutor.java:273)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> DefaultLifecycleExecutor.java:140)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
> :315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
> :430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: There are test
> failures.
>         at org.apache.maven.plugin.surefire.SurefirePlugin.execute(
> SurefirePlugin.java:403)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
> DefaultPluginManager.java:412)
>         at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
> DefaultLifecycleExecutor.java:534)
>         ... 16 more
> [INFO]
> ------------------------------------------------------------------------
> 
> 
> 
> 
> 
> On 11/1/06, Kay Huber <[EMAIL PROTECTED]> wrote:
>>
>>
>> Hi Binil
>>
>> The good news first:
>> Thanks to your work, I got the right start - and found the answer to your
>> final question :-)
>>
>> I verified each entry in the dependencies list of the plugins pom.xml and
>> found the following dependencies to be necessary (only those are required
>> -
>> you can delete the others):
>>
>> - org.apache.maven:maven-project:jar:2.0.2
>> - org.apache.maven:maven-settings:jar:2.0.2
>> - org.apache.maven:maven-plugin-api:jar:2.0.2
>> - org.apache.maven.scm:maven-scm-api:jar:1.0-beta-3
>> - org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-beta-3
>> - org.apache.maven.scm:maven-scm-provider-svnexe:jar:1.0-beta-3
>>
>> All other scm's are not required because at the moment the plugin can
>> deal
>> with svn only anyway.
>> Please note, that the above versions are all available from ibiblio.org
>> directly - no need to use any SNAPSHOTS and therefore no need to include
>> the
>> http://people.apache.org/maven-snapshot-repository/ repository anymore.
>>
>> I hope that helps for you too! At least it runs for me now - if there's
>> still some problem left, just ask - I might have forgotten something ;-)
>>
>> Ah, the bad news by the way: The maven-buildnumber-plugin itself is not
>> available from http://commons.ucalgary.ca/pub/m2-snapshots any longer as
>> it
>> seems. http://commons.ucalgary.ca seems to have just "suffered" a
>> redesign
>> -
>> likely the pub-storage has been forgotten by the webdesigner... :-(
>>
>> You can still download and compile the plugin manually however. Just use
>> the
>> svn connection:
>> http://apollo.ucalgary.ca:8800/maven-buildnumber-plugin/trunk
>>
>> Regards,
>> Kay
>>
>>
>> Binil Thomas wrote:
>> >
>> > Hi all,
>> >
>> > I am running into a 'java.lang.NoClassDefFoundError:
>> > org/apache/maven/scm/provider/svn/command/SvnCommandLineUtils' trying
>> to
>> > use the maven-buildnumber plugin. I am aware that this plugin is
>> developed
>> > outside of Apache or Codehaus, but since the plugin does not seem to
>> have
>> > a mailinglist of its own I am posting this here hoping to get the
>> > attention of the original author Julian Wood or someone else who has
>> > successfully used this plugin.
>> >
>> > I followed the instructions mentioned at
>> >
>> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/install.html
>> > and
>> >
>> http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html.
>> > When I ran mvn compile, the build failed as it was unable to download 8
>> > dependencies - all requried by the maven-buildnumber plugin. The
>> missing
>> > dependencies were:
>> >
>> >    1)
>> >
>> org.apache.maven.scm:maven-scm-provider-starteam:jar:1.0-beta-3-SNAPSHOT
>> >    2)
>> > org.apache.maven.plugins:maven-release-plugin:jar:2.0-beta-4-SNAPSHOT
>> >    3) org.apache.maven.scm:maven-scm-api:jar:1.0-beta-3-SNAPSHOT
>> >    4)
>> org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-beta-3-SNAPSHOT
>> >    5)
>> > org.apache.maven.scm:maven-scm-manager-plexus:jar:1.0-beta-3-SNAPSHOT
>> >    6)
>> org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-beta-3-SNAPSHOT
>> >    7)
>> >
>> org.apache.maven.scm:maven-scm-provider-clearcase:jar:1.0-beta-3-SNAPSHOT
>> >    8)
>> >
>> org.apache.maven.scm:maven-scm-provider-perforce:jar:1.0-beta-3-SNAPSHOT
>> >
>> > After some googling, I found the Apache snapshot repository at
>> > http://people.apache.org/maven-snapshot-repository/ hosts these
>> > dependencies. I tried adding the apache repository to my pom, but it
>> did
>> > not work. So I added the repository to the maven-buildnumber plugins
>> pom
>> > and it downloaded all except two dependencies. The missing ones this
>> time
>> > was:
>> >
>> >    1)
>> org.apache.maven.scm:maven-scm-provider-cvs:jar:1.0-beta-3-SNAPSHOT
>> >    2)
>> org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-beta-3-SNAPSHOT
>> >
>> > I edited the plugins pom again to refer to the
>> > org.apache.maven.scm:maven-scm-provider-cvsexe:jar and
>> > org.apache.maven.scm:maven-scm-provider-svnexe:jar dependencies.
>> >
>> > After this I ran mvn -Dmaven.buildNumber.skipCheck=true
>> > -Dmaven.buildNumber.skipUpdate=true compile and I got the following
>> error:
>> >
>> > java.lang.NoClassDefFoundError:
>> > org/apache/maven/scm/provider/svn/command/SvnCommandLineUtils
>> >         at
>> > org.codehaus.mojo.buildNumber.SvnInfoCommand.createCommandline(
>> SvnInfoCommand.java:93)
>> >         at
>> > org.codehaus.mojo.buildNumber.SvnInfoCommand.executeInfoCommand(
>> SvnInfoCommand.java:57)
>> >         at
>> > org.codehaus.mojo.buildNumber.SvnInfoCommand.executeCommand(
>> SvnInfoCommand.java:101)
>> >         at
>> > org.apache.maven.scm.command.AbstractCommand.execute(
>> AbstractCommand.java:55)
>> >         at
>> > org.codehaus.mojo.buildNumber.BuildNumberMojo.info(BuildNumberMojo.java
>> :444)
>> >         at
>> > org.codehaus.mojo.buildNumber.BuildNumberMojo.getRevision(
>> BuildNumberMojo.java:413)
>> >         at
>> > org.codehaus.mojo.buildNumber.BuildNumberMojo.execute(
>> BuildNumberMojo.java:310)
>> >         at
>> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(
>> DefaultPluginManager.java:412)
>> >         at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
>> DefaultLifecycleExecutor.java:534)
>> >         at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle
>> (DefaultLifecycleExecutor.java:475)
>> >         at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
>> DefaultLifecycleExecutor.java:454)
>> >         at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
>> (DefaultLifecycleExecutor.java:306)
>> >         at
>> >
>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
>> DefaultLifecycleExecutor.java:273)
>> >         at
>> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
>> DefaultLifecycleExecutor.java:140)
>> >         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
>> :322)
>> >         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> >         at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
>> >         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> >         at
>> > sun.reflect.NativeMethodAccessorImpl.invoke(
>> NativeMethodAccessorImpl.java:39)
>> >         at
>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(
>> DelegatingMethodAccessorImpl.java:25)
>> >         at java.lang.reflect.Method.invoke(Method.java:585)
>> >         at
>> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> >         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> >         at
>> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> >         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> >
>> > Looks like the SNAPSHOT dependencies have changed since this plugin was
>> > last built. Is anyone actively maintaining this plugin? The
>> functionality
>> > provided would be very useful for my team; so has anyone got this
>> working?
>> >
>> > Thanks,
>> > Binil
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Maven-buildnumber-plugin-tf2322368s177.html#a7118873
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> 
> Thanks
> 
> DJ MICK
> http://www.djmick.com
> http://www.myspace.com/mickknutson
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-buildnumber-plugin-tf2322368s177.html#a7130890
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Reply via email to