[
https://issues.apache.org/jira/browse/ZOOKEEPER-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449698#comment-16449698
]
ASF GitHub Bot commented on ZOOKEEPER-2983:
-------------------------------------------
Github user anmolnar commented on the issue:
https://github.com/apache/zookeeper/pull/469
@phunt This approach is a bit prettier and might help diagnose
classpath-related problems on build servers, but I can live without it. Given
that we're migrating to Maven, this patch wouldn't make any difference now.
> Print the classpath when running compile and test ant targets
> -------------------------------------------------------------
>
> Key: ZOOKEEPER-2983
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2983
> Project: ZooKeeper
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.5.3, 3.4.11
> Reporter: Mark Fenes
> Assignee: Mark Fenes
> Priority: Major
>
> Printing the classpath helps to verify that we have only the intended
> classes, jars on the classpath, e.g. clover.jar is included only when running
> coverage tests.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
