[
https://issues.apache.org/jira/browse/ZOOKEEPER-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370522#comment-16370522
]
ASF GitHub Bot commented on ZOOKEEPER-2983:
-------------------------------------------
Github user afine commented on a diff in the pull request:
https://github.com/apache/zookeeper/pull/469#discussion_r169435681
--- 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">
+ <pathconvert pathsep="${line.separator}| |-- "
property="echo.compile.classpath" refid="java.classpath"/>
--- End diff --
I found a "one-liner" for this here:
http://ant.apache.org/manual/using.html#pathshortcut
For example:
```xml
<echo>${toString:java.classpath}</echo>
```
What do you think?
> 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)
