Thomas Dudziak commented on ZOOKEEPER-537:

@Patrick: I can make a stab at the build.xml later this week.

@Hiram: Well, I'm no expert in GWT, but doesn't it have to be this way so that 
GWT compiles the java source code on the fly in a web application (quite 
similar to JSP pages) ? But this then means that you're not depending on the 
GWT build as a library, and you thus won't get any dependency conflicts because 
you happen to have another conflicting version on the classpath. And this is 
exactly the problem with zookeeper: Maven sees source files in the jar and 
compiles them, so I'll get zookeeper classes in my jar which then can conflict 
with some other version of zookeeper that I might have on the classpath.

> 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