[
https://issues.apache.org/jira/browse/ZOOKEEPER-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761036#action_12761036
]
Patrick Hunt commented on ZOOKEEPER-537:
----------------------------------------
For some reason hadoop does it this way, we inherited their basic build
structure. I don't see why we couldn't provide build artifacts like you suggest
(although others may disagree. this is the first time we've ever heard of this
issue, it is not a recent change), however my point before was addressed to the
fact that currently released/published artifacts include the source. Unless you
want to wait for this to be resolved and a new release shipped, it would be
good to find a workable solution for what we have today. I'm not familiar
enough with maven, hence my suggestion that you talk with someone who is.
> 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.
