|
The Usage example (http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html) causes a null pointer exception with
>mvn clean install eclipse:eclipse
java.lang.NullPointerException: The scm url cannot be null.
at org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:183)
at org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:794)
at org.codehaus.mojo.build.CreateMojo.getRevision(CreateMojo.java:704)
at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:455)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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:597)
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)
We use Mercurial (not svn), so from :
http://mojo.codehaus.org/buildnumber-maven-plugin/faq.html#missing-scm
Suggests adding <revisionOnScmFailure/>
I tried
<revisionOnScmFailure>unavailable</revisionOnScmFailure>
<doCheck>false</doCheck>
<doUpdate>false</doUpdate>
The following file is generated:
#maven.buildNumber.plugin properties file
#Thu May 31 14:03:19 BST 2012
buildNumber=6
However the jar file is tagged "-null"
Doesn't seem to follow conventions/principles of
"minimal coupling": why coupled to svn.
"least surprise": should fail safe.
"convention not configuration": should use valid defaults.
|
