[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #55174] java warning about java.system.class.l
From: |
Shane |
Subject: |
[Octave-bug-tracker] [bug #55174] java warning about java.system.class.loader property |
Date: |
Fri, 8 May 2020 01:17:19 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.149 Safari/537.36 OPR/67.0.3575.115 |
Follow-up Comment #7, bug #55174 (project octave):
It appears that this flag has been passed to the JVM since Java support was
first added to Octave in 2012 by JWE:
https://github.com/NexMirror/Octave/commit/47a9b9ca1239e9343c88e39905567fc206b285ea
Based on the comments in OctClassLoader.java, it seems this was mainly a
workaround to a bug in an old Sun JVM:
// Look dynamically into java.library.path, because Sun VM does
// not do it (seems to cache initial java.library.path instead)
However, OctClassLoader is also used in ClassHelper.java, which is used more
widely in ov-java.cc. ClassHelper seems to be the piece that marshals Octave
calls to Java, and it runs its own class loader.
https://github.com/NexMirror/Octave/blob/master/scripts/java/org/octave/ClassHelper.java
Therefore, although I'm not fully confident, I think it is probably safe to
make OctClassLoader not be the default class loader, since it is wrapped by
ClassHelper anyway.
A reasonable resolution to this ticket might be:
1. Apply Philip's patch
2. Fix the following documentation in ov-java.cc that mentions
OctClassLoader:
https://github.com/NexMirror/Octave/blob/eda9e9f0f053da5a05b11a897f6f8043b70ae9c8/libinterp/octave-value/ov-java.cc#L620
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?55174>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/