[ 
https://jira.codehaus.org/browse/MRELEASE-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MRELEASE-833:
------------------------------------

    Description: 
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.
{code:xml}
<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>
{code}
Circumvention: Duplicating the Plugin Dependency as an explicit dependency in 
the POM forces release:prepare to catch the problem.
{code:xml}
<dependency>
  <groupId>org.example</groupId>
  <artifactId>my-findbugs-filters</artifactId>
  <version>0.1-SNAPSHOT</version>
  <scope>provided</scope>
</dependency>
{code}

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


    
> 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
>            Assignee: Robert Scholte
>
> 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.
> {code:xml}
> <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>
> {code}
> Circumvention: Duplicating the Plugin Dependency as an explicit dependency in 
> the POM forces release:prepare to catch the problem.
> {code:xml}
> <dependency>
>   <groupId>org.example</groupId>
>   <artifactId>my-findbugs-filters</artifactId>
>   <version>0.1-SNAPSHOT</version>
>   <scope>provided</scope>
> </dependency>
> {code}

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

Reply via email to