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 Wed, 21 Feb 2018 16:29:00 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2983:
-------------------------------------------

Github user mfenes commented on a diff in the pull request:

    https://github.com/apache/zookeeper/pull/469#discussion_r169695831
  
    --- Diff: build.xml ---
    @@ -1861,4 +1861,18 @@ xmlns:cs="antlib:com.puppycrawl.tools.checkstyle.ant">
            <delete dir="${build.dir.eclipse}" />
          </target>
     
    +    <target name="print_compile_classpath">
    --- End diff --
    
    True, my intention with the "_" was to indicate that these targets are purely utility
targets i.e. it does not make too much sense to run them individually, unlike clean, compile,
test-core-java etc. targets. If you don't like this idea, I can replace the "_"-s with "-"-s
if you wish.


> 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)

Mime
View raw message