Mahadev konar commented on ZOOKEEPER-537:

the only reason I feel strongly about this is the following- 

- we have had a lot of production installations for hadoop and zookeeper. I 
have been invloved in supporting both of them. One thing I have found while 
supporting these frameworks/services is that folks tend to sometime add patches 
to there specific installations. So, having source code as an artifact of the 
release makes it easy for folks like me (developers), wherein we can take a 
look at the code sometimes (when all else fails) and find out what this source 
code contains or what changes it might have  (different from the real apache 
release, sometimes that information gets missing as well).  

are you proposing a seperate source jar as a part of release artifact as well? 

> 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