added some common test infrastructure to the jdk test library for testing multi-release Jar files. There is a problematic dependency from jdk/test/lib/testlibrary/java/util/jar/CreateMultiReleaseTestJars.java on sun.security.tools.jarsigner.Main. The issue is that any test that causes the compilation of classes in the test library may trigger the compilation of CreateMultiReleaseTestJars, which will fail in jigsaw/jake as it tries to access a type in a non-exported package.
It is not an acceptable solution for all tests using the test library to have to declare an explicit dependency on sun.security.tools.jarsigner, since most of them will not use CreateMultiReleaseTestJars.
Is it possible to use a supported API for signing? Or refactor the code so that the dependency is local to the test using it.