You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jieryn (JIRA)" <ji...@codehaus.org> on 2013/09/24 17:07:52 UTC
[jira] (MENFORCER-164) bannedDependencies searchTransitive=false
failure
jieryn created MENFORCER-164:
--------------------------------
Summary: bannedDependencies searchTransitive=false failure
Key: MENFORCER-164
URL: https://jira.codehaus.org/browse/MENFORCER-164
Project: Maven Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 1.3.1
Reporter: jieryn
The bannedDependencies rule is too aggressive, especially when you have searchTransitive=false configured. Here is an example pom.xml which demonstrates the problem:
{code}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.apache.maven.plugins.enforcer</groupId>
<artifactId>banned-dependencies</artifactId>
<version>1-SNAPSHOT</version>
<dependencies>
<dependency>
<groupId>org.springframework.ldap</groupId>
<artifactId>spring-ldap-core</artifactId>
<version>1.3.2.RELEASE</version>
</dependency>
</dependencies>
<build>
<defaultGoal>validate</defaultGoal>
<plugins>
<plugin>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.3.1</version>
<executions>
<execution>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<bannedDependencies>
<excludes>
<exclude>commons-lang:commons-lang</exclude>
</excludes>
</bannedDependencies>
</rules>
<searchTransitive>false</searchTransitive>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
{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