[ZOOKEEPER-721] Minor cleanup related to the log4j version change from 1.2.15 -> 1.2.16

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.5.0
• Component/s: build
• Labels: ivy maven
• Hadoop Flags: Reviewed
• Assignee: Sean Busbey
• Reporter: Paolo Castagna
• Created: 21/Mar/10 08:25
• Updated: 12/Dec/12 11:05
• Resolved: 12/Dec/12 07:32

Description

The generated Maven pom.xml file contains:

<dependency>
  <groupId>log4j</groupId>
  <artifactId>log4j</artifactId>
  <version>1.2.15</version>
  <scope>compile</scope>
</dependency>

It would be better to have:

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

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.