Patrick Hunt updated ZOOKEEPER-537:

    Status: Open  (was: Patch Available)

Thomas there are at least a couple of outstanding comments not addressed by 
this patch, specifically there
is interest to not change the existing jar file as it is currently used for 
those non-maven users.. I put forth the
idea to have a separate set of jars for bin/src/jdoc (btw, I don't see the jdoc 
jar in your patch, isn't that something
you had mentioned would be useful?)



Do you see an issue with what I'm suggesting?

> 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.3.0
>            Reporter: Thomas Dudziak
>             Fix For: 3.3.0
>         Attachments: build.patch
> 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