Page 1 of 1

warning on windows 10

Posted: Wed Apr 03, 2019 6:33 pm
by sderrick
When our sdk editor loads on windows 10 I see the following warning

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by ro.sync.ui.te (files:c:/Users/Scott/Desktop/ide/oxygen-21.0.0.0.jar) to field javax.swing.text.DefaultHighLighter.highlights

Scott

Re: warning on windows 10

Posted: Thu Apr 04, 2019 11:14 am
by Radu
Hi Scott,

What Java version are you using to run the component? Indeed sometimes we are using reflection in our code and newer Java versions report this as a warning.

Regards,
Radu

Re: warning on windows 10

Posted: Thu Apr 04, 2019 5:42 pm
by sderrick
on my windows test machine its running 11.0.2

Scott

Re: warning on windows 10

Posted: Fri Apr 05, 2019 8:30 am
by Radu
Hi Scott,

We'll try to fix this warning on our side in a future version, for now you can ignore it.

Regards,
Radu

Re: warning on windows 10

Posted: Thu Apr 09, 2020 6:37 pm
by sderrick
When loading the SDK on my linux box.

I thought this had been fixed in version 22.0?

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by ro.sync.ui.qe (file:/home/scott/.m2/repository/com/oxygenxml/oxygen/22.0.0.0/oxygen-22.0.0.0.jar) to field javax.swing.text.DefaultHighlighter.highlights
WARNING: Please consider reporting this to the maintainers of ro.sync.ui.qe
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Scott

Re: warning on windows 10

Posted: Fri Apr 10, 2020 8:08 am
by Radu
Hi Scott,

Oxygen and its Author Component still show in the command line a couple of similar warnings when being run with Java 9 or newer.
I have issues logged on my side to remove these warnings. Honestly there are some warnings like this one you encountered which I'm not sure how I could resolve. For this I would need to copy and maintain on our side a bunch of classes from the Swing package, classes which may differ between Java versions. So I will probably postpone fixing these problems until Java removes completely the possibility to call by reflection methods from its packages.

Regards,
Radu