Kristian Waagan <[EMAIL PROTECTED]> writes: > Another proposal, which *I think* allow us to keep things as they are > and generate a separate jar file for unit tests requiring > package-private access: > Use the non-standard option -Xbootclasspath. > > By specifying the jars on the boot classpath, the sealing protection > will be overridden and the tests can be run. We can keep the existing > tests as they are, and only use this option when running the > "package-private unit tests". This approach also require two > (currently three) steps to run all tests, but we won't have to change > the existing jars. The unit tests can then also be run with > distribution jars if anyone should wish to do that, and with both sane > and insane builds. > > Does anyone see any showstoppers for this approach?
Sounds like a win-win to me... -- dt
