Open GoogleCodeExporter opened 8 years ago
I am also getting this problem. I am running it on Ant 1.7 with JDK
1.6.0_10-b33.
Original comment by faisal.a...@gmail.com
on 20 Jan 2009 at 10:18
I am too! Any help will be appreciated.
Original comment by morrbrad...@gmail.com
on 27 Jan 2009 at 11:35
I could work around this by including the packaged jar to be checked rather
than
.class files in the classpath. It seems to expect jars only. This wasn't the
best
solution for me as I had to place the execution of the check in an unexpected
phase
of the build.
Original comment by leonfranzen@gmail.com
on 30 Jan 2009 at 10:30
Also having this same issue. I think that expecting the classes that are going
to be
analyzed to be in a JAR package is unnecessary.
Original comment by Octavius@gmail.com
on 27 Feb 2009 at 5:55
IMHO the example http://code.google.com/p/testability-explorer/wiki/AntTask is
misleading:
<classpath>
<fileset dir="lib">
<include name="*.jar"/>
</fileset>
<fileset dir="build/classes">
<include name="com/ownstuff/**"/>
</fileset>
</classpath>
It should be:
<classpath>
<fileset dir="lib">
<include name="*.jar"/>
</fileset>
<pathelement location="build/classes"/>
</classpath>
Original comment by gslowiko...@gmail.com
on 2 Mar 2009 at 1:15
That pathelement location syntax fixed the problem. Thanks.
Original comment by mgaer...@gmail.com
on 15 Jul 2009 at 6:22
Original issue reported on code.google.com by
mgaer...@gmail.com
on 18 Jan 2009 at 6:45