Optionally run tests on the boot classpath

[Google Code Exporter]

When writing class library tests, it is convenient to use the same package name 
as the code 
under test, leading to tests with names like "java.util.HashMapTest". HotSpot 
refuses to load 
"java.*" tests on the application classpath, so we should load them on the boot 
classpath. 
Perhaps with a command line argument, so things run on the application 
classpath by default.

Original issue reported on code.google.com by [e-mail] on 23 Apr 2010 at 9:26

[Google Code Exporter]

Original comment by [e-mail] on 19 May 2010 at 12:39

• Changed state: Done