NullPointer when Releasing without <configuration> node in the
maven-release-plugin
-----------------------------------------------------------------------------------
Key: CONTINUUM-1527
URL: http://jira.codehaus.org/browse/CONTINUUM-1527
Project: Continuum
Issue Type: Bug
Components: Release
Affects Versions: 1.1-beta-3
Reporter: Yudong Wang
If a pom file contains following, which is correct:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
</plugin>
In the web ui, choose prepare release, this will cause NullPointerException at:
org.apache.maven.continuum.web.action.ReleasePrepareAction.getReleasePluginParameters(ReleasePrepareAction.java:142)
if ( plugin.getGroupId() != null && plugin.getGroupId().equals(
"org.apache.maven.plugins" ) &&
plugin.getArtifactId() != null &&
plugin.getArtifactId().equals( "maven-release-plugin" ) )
{
Xpp3Dom dom = (Xpp3Dom) plugin.getConfiguration();
line 142 Xpp3Dom configuration = dom.getChild(
"releaseLabel" );
Cause:
Since the plugin defines no <configuration> node, plugin.getConfiguration()
returns null
Workaround:
add empty <configuration>, for example:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<!-- empty configuration node when we have
nothing to configure, this is needed due a bug in continuum 1.1-beta-3 -->
</configuration>
</plugin>
--
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
