Execution from packaged jar fails

[GoogleCodeExporter]

Within our environment it is necessary to execute the tests from the packaged 
jar file. This fails because WildcardPatternSuite.getBaseDir() returns a File. 
For us it would be better if it would return an InputStream instead.

What steps will reproduce the problem?
You can reproduce the problem by following the steps described on:
http://stackoverflow.com/questions/18055189/why-my-uri-is-not-hierarchical

What is the expected output? What do you see instead?
Expected is a runing test suite.
Instead I get an exception:
Testcase: initializationError(<myPackage>.MyUnitTests): 
Caused an ERROR URI is not hierarchical
java.lang.IllegalArgumentException: URI is not hierarchical
   at java.io.File.<init>(File.java:363)
   at com.googlecode.junittoolbox.WildcardPatternSuite.getBaseDir(WildcardPatternSuite.java:135)
   at com.googlecode.junittoolbox.WildcardPatternSuite.findSuiteClasses(WildcardPatternSuite.java:59)
   at com.googlecode.junittoolbox.WildcardPatternSuite.getSuiteClasses(WildcardPatternSuite.java:54)
   at com.googlecode.junittoolbox.WildcardPatternSuite.<init>(WildcardPatternSuite.java:180)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)


What version of the product are you using? On what operating system?
Version 1.5
Windows 7 environment

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 23 Jan 2014 at 1:41

[GoogleCodeExporter]

Original comment by michael.tamm2 on 16 Jun 2014 at 7:52

• Changed state: Accepted

[GoogleCodeExporter]

If you would like to contribute a patch to fix this bug for your situation, I'm 
more than happy to merge it into the code base.

Original comment by michael.tamm2 on 16 Jun 2014 at 8:03

[GoogleCodeExporter]

I'm getting this issue/error while attempting to run the tests from within a 
compiled jar on an Linux arm chip (using an embedded version of Java 1.8). We 
are compiling with maven and have included the apache dependency.

For reference here is the java version we are running with:
java version "1.8.0"
Java(TM) SE Embedded Runtime Environment (build 1.8.0-b132, profile compact2, 
headless)
Java HotSpot(TM) Embedded Client VM (build 25.0-b70, mixed mode)

Original comment by [email protected] on 16 Jun 2014 at 8:33

[GoogleCodeExporter]

Original comment by michael.tamm2 on 17 Jun 2014 at 7:13

• Changed state: Started

[GoogleCodeExporter]

Original comment by michael.tamm2 on 28 Jan 2015 at 10:25

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[MichaelCowanPdx]

Any updates on this? It is still happening.

[hsyed]

Can't run the tests from bazel as the tests are always run from a packaged jar.

[JohannesRudolph]

Same issue here. Anyone have details where exactly junit-toolbox needs to be fixed?