Closed radai-rosenblatt closed 9 years ago
on further thought the cause of the original exception probably isnt exactly the jdk bug i linked to (since its marked as solved in the jdk i'm running), but something similar cause by onejar's packaging (jars within jars)
Che the unit test. There have similar thing:
_exportFile = new ExportFile(ClassLoader.getSystemResource("org/dcache/nfs/exports").toURI());
any URI will fail if the resource is 2 jars deep (inside a *.jar inside a onejar)
Can one of the admins verify this patch?
ok to test
Thanks!
retest this please
allow parsing the exports "file" directly from a stream.
this is needed as a work around to something like this issue - http://bugs.java.com/bugdatabase/view_bug.do?bug_id=7156873
specifically, if you use onejar packaging, and try something like:
(where "exports" is packaged inside the jar), you will get this:
with this commit you can do this: