[jira] Commented: (MRELEASE-108) NullPointerException when POM has no SCM connection url

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (MRELEASE-108) NullPointerException when POM has no SCM connection url

JIRA jira@codehaus.org
    [ http://jira.codehaus.org/browse/MRELEASE-108?page=comments#action_79064 ]
           
Tom Parker commented on MRELEASE-108:
-------------------------------------

this seems to be fixed in the latest snapshot version

> NullPointerException when POM has no SCM connection url
> -------------------------------------------------------
>
>                 Key: MRELEASE-108
>                 URL: http://jira.codehaus.org/browse/MRELEASE-108
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4
>         Environment: mvn 2.0.4 WinXP
>            Reporter: Marcel Schutte
>         Attachments: preparereleasemojo.patch
>
>
> When a POM has no SCM connection url, but only developerConnection, release:prepare fails with a NullPointerException. We don't have separate read-only access to our cvs repository, which is why there is only a developerconnection.
> C:\Data\WSAD\MijnOhra\MavenParent>mvn release:prepare
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Super POM voor alle OHRA maven2 projecten
> [INFO]    task-segment: [release:prepare] (aggregator-style)
> [INFO] ----------------------------------------------------------------------------
> [INFO] [release:prepare]
> [INFO] Verifying that there are no local modifications...
> [INFO] Executing: cvs -z3 -f -d :pserver:schuttem@anhas053:/framework -n -q update -d
> [INFO] Working directory: C:\Data\WSAD\MijnOhra\MavenParent
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "Super POM voor alle OHRA maven2 projecten"? (nl.ohra:MavenParent) 01.08: :
> What is SCM release tag or label for "Super POM voor alle OHRA maven2 projecten"? (nl.ohra:MavenParent) MavenParent-01.08: :
> What is the new development version for "Super POM voor alle OHRA maven2 projecten"? (nl.ohra:MavenParent) 01.09-SNAPSHOT: :
> [INFO] Transforming 'Super POM voor alle OHRA maven2 projecten'...
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] null
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.NullPointerException
>         at java.util.Hashtable.put(Hashtable.java:393)
>         at java.util.Properties.setProperty(Properties.java:102)
>         at org.apache.maven.plugins.release.config.PropertiesReleaseConfigurationStore.write(PropertiesReleaseConfigurationStore.java:225)
>         at org.apache.maven.plugins.release.config.PropertiesReleaseConfigurationStore.write(PropertiesReleaseConfigurationStore.java:149)
>         at org.apache.maven.plugins.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:145)
>         at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:108)
>         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.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:219)
>         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:324)
>         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)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26 seconds
> [INFO] Finished at: Tue May 16 12:59:28 CEST 2006
> [INFO] Final Memory: 4M/8M
> [INFO] ------------------------------------------------------------------------
> The attached fix tests scm.getConnection() before using it.

--
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