You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Kreussling (JIRA)" <ji...@codehaus.org> on 2013/04/05 18:52:52 UTC

[jira] (MRELEASE-833) release:prepare allows SNAPSHOT Plugin Dependencies

Chris Kreussling created MRELEASE-833:
-----------------------------------------

             Summary: release:prepare allows SNAPSHOT Plugin Dependencies
                 Key: MRELEASE-833
                 URL: https://jira.codehaus.org/browse/MRELEASE-833
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
          Components: prepare
    Affects Versions: 2.4
         Environment: Maven 2.2.1
            Reporter: Chris Kreussling


When a Plugin Dependency references a SNAPSHOT version, release:prepare doesn't flag it. This allows a POM with SNAPSHOT dependencies on Plugins to be released.

Example: This uses the FindBugs Plugin as an example, because that's what tripped us up. release:prepare didn't catch this. I suspect the same problem will occur for any Plugin Dependency that relies on a SNAPSHOT.

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>findbugs-maven-plugin</artifactId>
  <dependencies>
    <dependency>
      <groupId>org.example</groupId>
      <artifactId>my-findbugs-filters</artifactId>
      <version>0.1-SNAPSHOT</version>
    </dependency>
  </dependencies>
  <configuration>
    <includeFilterFile>include.xml</includeFilterFile>
    <excludeFilterFile>exclude.xml</excludeFilterFile>
  </configuration>
  <executions>
    <execution>
      <goals>
        <goal>check</goal>
      </goals>
    </execution>
  </executions>
</plugin>

Circumvention: Duplicating the Plugin Dependency as an explicit dependency in the POM forces release:prepare to catch the problem.

<dependency>
  <groupId>org.example</groupId>
  <artifactId>my-findbugs-filters</artifactId>
  <version>0.1-SNAPSHOT</version>
  <scope>provided</scope>
</dependency>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira