The test AbsPathInImage.java was added to guard against accidentally leaking absolute paths from the build environment into the product image. This test currently has an exception on Windows for jvm.dll, where we cannot get rid of sometimes resolving the __FILE__ macro in C++ into absolute paths in the binary. Until we have a way to mitigate this with the toolchain we use, we just have to live with the exception.

The recent changes to jdk.incubating.jpackage triggered another one of these situations. One of the binaries that get bundled as a resource there now has an absolute path to a header in it. This binary is also built from C++.

This patch adds another explicit exception to the test for this particular case.

Bug: https://bugs.openjdk.java.net/browse/JDK-8243510

Webrev: http://cr.openjdk.java.net/~erikj/8243510/webrev.01/

/Erik

Reply via email to