[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mahadev konar updated ZOOKEEPER-721:
------------------------------------

    Fix Version/s:     (was: 3.3.1)

moving this out to 3.4.

> No <exclusions> set for log4j dependency in the generated pom.xml
> -----------------------------------------------------------------
>
>                 Key: ZOOKEEPER-721
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-721
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.3.0
>            Reporter: Paolo Castagna
>            Priority: Minor
>             Fix For: 3.4.0
>
>
> The generated Maven pom.xml file contains:
> {code}
> <dependency>
>   <groupId>log4j</groupId>
>   <artifactId>log4j</artifactId>
>   <version>1.2.15</version>
>   <scope>compile</scope>
> </dependency>
> {code}
> It would be better to have:
> {code}
> <dependency>
>   <groupId>log4j</groupId>
>   <artifactId>log4j</artifactId>
>   <version>1.2.15</version>
>   <scope>compile</scope>
>   <exclusions>
>     <exclusion>
>       <groupId>javax.jms</groupId>
>       <artifactId>jms</artifactId>
>     </exclusion>
>     <exclusion>
>       <groupId>com.sun.jdmk</groupId>
>       <artifactId>jmxtools</artifactId>
>     </exclusion>
>     <exclusion>
>       <groupId>com.sun.jmx</groupId>
>       <artifactId>jmxri</artifactId>
>     </exclusion>
>     <exclusion>
>       <groupId>javax.mail</groupId>
>       <artifactId>mail</artifactId>
>     </exclusion>
>   </exclusions> 
> </dependency>
> {code}
> This would avoid to people depending on ZooKeeper artifacts the pain to 
> exclude such "broken" dependencies by themselves.
> A similar issue is discussed in HADOOP-6629, although I am not clear on how 
> to solve fix it using Ivy.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to