[
http://jira.codehaus.org/browse/MOJO-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206816#action_206816
]
Jon Osborn commented on MOJO-1463:
----------------------------------
I'm confirming that rolling back to 1.0-beta-3 makes the issue go away. Please
fixup for beta5.
> java.lang.NullPointerException: The scm url cannot be null. after update to
> 1.0-beta-4
> --------------------------------------------------------------------------------------
>
> Key: MOJO-1463
> URL: http://jira.codehaus.org/browse/MOJO-1463
> Project: Mojo
> Issue Type: Bug
> Components: buildnumber
> Environment: Maven 2.2.1
> Reporter: Dennis Kieselhorst
> Priority: Critical
>
> Updated from 1.0-beta-3 to 1.0-beta-4.
> Seems that ${project.scm.developerConnection} is now required.
> ${project.scm.connection} is configured but not used as an alternative.
> java.lang.NullPointerException: The scm url cannot be null.
> at
> org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:181)
> at
> org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:722)
> at
> org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:593)
> at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:452)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleE
> xecutor.java:332)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> 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)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
