Brian Schack created LANG-1383:

             Summary: Illegal Reflective Access Operation
                 Key: LANG-1383
             Project: Commons Lang
          Issue Type: Bug
          Components: lang.builder.*
    Affects Versions: 3.7
            Reporter: Brian Schack

ReflectionToStringBuilder::toString prints an illegal access warning to 
System.err. The warning suggests to report this issue to the Apache Commons 

Boolean.TRUE is such a simple value that I don't really need 
ReflectionToStringBuilder. But more complex types (such as HashMap) print the 
same warning. I chose Boolean.TRUE in order to simplify this example.

When I searched for this warning message, I found a StackOverflow answer which 
suggested to report it to the package maintainers ([JDK9: An illegal reflective 
access operation has occurred. 

I also asked my own StackOverflow question about how to throw an exception for 
this warning ([How can I throw an exception for an illegal reflective access 

I will try to change my code to avoid this warning, but it also seems that 
Apache Commons should not cause the warning. Perhaps it could use different 
methods to get the values of the fields, or skip the private fields, or throw 
an exception? The warning message suggests that the Java maintainers want the 
Apache Commons maintainers to avoid this warning. And when they disable this 
illegal access in the future, then it could impact Apache Commons.


{{import org.apache.commons.lang3.builder.*;}}
{{class Test {}}

{{public static void main(String[] args) {}}





{{WARNING: An illegal reflective access operation has occurred}}
{{ WARNING: Illegal reflective access by 
{{ mons-lang3-3.7/commons-lang3-3.7.jar) to field java.lang.Boolean.value}}
{{ WARNING: Please consider reporting this to the maintainers of 
{{ 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}}

This message was sent by Atlassian JIRA

Reply via email to