zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2983) Print the classpath when running compile and test ant targets
Date Tue, 24 Apr 2018 00:18:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449077#comment-16449077

ASF GitHub Bot commented on ZOOKEEPER-2983:

Github user phunt commented on the issue:

    @mfenes @anmolnar @afine   - ant already has a -d and a -v option, why do we need to add
additional? Is it really necessary that all the builds include this information? Why is -d/-v
not sufficient?

> 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

View raw message