Uploaded image for project: 'Continuum'
  1. Continuum
  2. CONTINUUM-1527

NullPointer when Releasing without <configuration> node in the maven-release-plugin

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.1-beta-3
    • 1.1-beta-4
    • Release
    • None

    Description

      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>

      Attachments

        Activity

          People

            evenisse Emmanuel Venisse
            yudongw Yudong Wang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment