Menu

#49 Ant DependencyReporter task behaves different from CLI app

open
Ant Tasks (2)
5
2014-08-25
2009-12-04
No

The ANT DependencyReporter task seems to behave differently than its CLI counterpart. The following:

<target name="finddeps" depends="jar">
    <dependencyextractor destfile="${tmp}/df.xml" xml="yes">
        <path>
            <pathelement location="${tmp}/myapp.jar"/>
        </path>
    </dependencyextractor>
    <dependencyreporter
        srcfile="${tmp}/df.xml"
        destfile="${tmp}/df.out"
        showinbounds="true"
        classfilter="true"
        featurescopeincludes="/^java/"
    />
</target>

Yields a different output than:

C:\dev\myapp\tmp> DependencyExtractor -xml c:\dev\myapp\tmp\myapp.jar | DependencyReporter -show-inbounds -class-filter -feature-scope-includes "/^java/" >df2.out

Looks like in ant, one must specify featurescope="true" and scopeincludes="expr" to get the same effect that is achieved by specifying "-feature-scope-includes" in the CLI.

Discussion


Log in to post a comment.