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]
