[
https://issues.apache.org/jira/browse/ZOOKEEPER-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761079#action_12761079
]
Thomas Dudziak commented on ZOOKEEPER-537:
------------------------------------------
Yes, all I'd like to see is separate zookeeper.jar and zookeeper-source.jar
(and zookeeper-javadoc.jar would also be nice). Having source code is
definitely a good thing because it makes debugging so much easier :-)
In the maven world you would get that automatically by adding something like
this to the build section in the POM
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<phase>verify</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
(and similarly for javadoc).
> 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.
