Patrick Hunt updated ZOOKEEPER-537:

    Fix Version/s:     (was: 3.2.1)

3.2.1 is out the door so moving this for consideration in 3.3. I know Hadoop in 
general does this (mr/hdfs/etc...) and Mahadev feels strongly about this 

Thomas, can't Maven handle this? Perhaps by explicitly excluding the zk classes 
in question from the generated jar (the one in your project I mean). Seems like 
a bug in Maven regardless (we don't see this in other build systems), perhaps 
you can followup by entering a JIRA against Maven itself?

> The zookeeper jar includes the java source files
> ------------------------------------------------
>                 Key: ZOOKEEPER-537
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-537
>             Project: Zookeeper
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>            Reporter: Thomas Dudziak
>             Fix For: 3.3.0
> This is a problem if you use zookeeper as a dependency in maven because for 
> whatever reason the maven compiler plugin will pick up the java files in the 
> jar and compile them to the output directory. From there they will land in 
> the generated jar file for whatever project happens to depend on zookeeper 
> thus introducing duplicate classes (once in zookeeper.jar, once in the 
> project's artifact).

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