[
https://issues.apache.org/jira/browse/ZOOKEEPER-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761024#action_12761024
]
Thomas Dudziak commented on ZOOKEEPER-537:
------------------------------------------
Every other open or closed source project I've worked with, separated these
into two jars, one just for the binary class files and additional resources,
and one only for the sources. In the maven world, you'd also see a third one
containing the javadoc. The reasons for that are several. For instance, a lot
of people still care about the size of a released artifact and a few kilobytes
actually matters to them. Also, all kinds of tools are build among these
assumptions. Take your usual Java IDE - you can point it at a jar containing
class files and it will happily use them. Or you tell it this other jar
contains source files, and it will link them. However if the jar contains both,
then you might encounter problems in the IDE because the assumption was that
they are actually separate jars.
> 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.
