Issue2705

classification
Title: Illegal reflective access
Type: Severity: normal
Components: Versions: Jython 2.5
Milestone:
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: jeff.allen, thadguidry
Priority: Keywords: Java Roadmap

Created on 2018-09-22.15:09:02 by thadguidry, last changed 2018-11-04.14:53:57 by jeff.allen.

Messages
msg12116 (view) Author: Thad Guidry (thadguidry) Date: 2018-09-22.15:09:01
Hi we use the Jython standalone jar in our OpenRefine project and have begun to notice these kinds of errors.  I saw previous issues by Jeff Allen, but do not know if this one is internal or external related.  So feel free to close and let us know the best course of action.

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.python.google.common.base.internal.Finalizer (file:/E:/Downloads/openrefine-win-3.1-SNAPSHOT/openrefine-3.1-SNAPSHOT/webapp/extensions/jython/module/MOD-INF/lib/jython-standalone-2.5.4-rc1.jar) to field java.lang.Thread.inheritableThreadLocals
WARNING: Please consider reporting this to the maintainers of org.python.google.common.base.internal.Finalizer
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
msg12117 (view) Author: Jeff Allen (jeff.allen) Date: 2018-09-22.16:33:33
It's the same problem in general as #2656, arising from Java 9+. We aim to eliminate these from Jython 2.7.2, which I expect we shall release this year. The project has insufficient effort to go back to 2.5.x with fixes, so your route out is via 2.7.x, or stick at Java 8.

A 2.7.0 or 2.7.1 would not be better from this perspective right now, but if you were to use them experimentally it would help prepare your code (and make a step towards a hoped-for 3.x). If non-english text is important to you, as it seems it might, you'll find good and bad here, with str support for UTF-16 gone/broken and increasing conformance to the Python 2.7 model as we go on.

The org.python prefix is the result of repackaging Google code with jarjar as a way to manage dependence on a particular version. However, I feel sure that if you launched with --illegal-access=warn, there would be many others.
History
Date User Action Args
2018-11-04 14:53:57jeff.allensetstatus: pending -> closed
2018-09-22 16:33:33jeff.allensetkeywords: + Java Roadmap
status: open -> pending
resolution: wont fix
messages: + msg12117
nosy: + jeff.allen
2018-09-22 15:09:02thadguidrycreate