Hadoop QA commented on ZOOKEEPER-537:
-1 overall. Here are the results of testing the latest attachment
against trunk revision 831486.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
Please justify why no tests are needed for this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
+1 findbugs. The patch does not introduce any new Findbugs warnings.
-1 release audit. The applied patch generated 184 release audit warnings
(more than the trunk's current 182 warnings).
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Release audit warnings:
This message is automatically generated.
> 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.3.0
> Reporter: Thomas Dudziak
> Fix For: 3.3.0
> Attachments: build.patch
> 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.