There is an inconsistency in searching classes vs resources if
bootclasspath contains an empty path. Empty path on bootclasspath is
skipped by the bootstrap class loader when searching classes while it
defaults to current working directory when searching resources as the
application class loader. This fixes sun.misc.Launcher to skip empty
path when constructing the paths from bootclasspath for resource lookup.
Webrev at:
http://cr.openjdk.java.net/~mchung/jdk9/webrevs/6760902/webrev.00/
There is some incompatibility risk that may impact existing code
depending on this behavior to search resources from the current working
directory if empty path (rather than explicit) is set. I think most
application using bootclasspath is to add their paths to load their
classes and likely expect the resources are looked in the consistent way
(i.e. skips the empty path). So I expect the incompatibility risk is low.
thanks
Mandy
