https://bz.apache.org/bugzilla/show_bug.cgi?id=63781
stefan.o...@googlemail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|REOPENED |RESOLVED
--- Comment #7 from stefan.o...@googlemail.com ---
Okay, the explanation is:
With --illegal-access=warn , the new canAccess()-check will return true, since
the access is still allowed. It will, however, log the warning (which might be
a little bit verbose, since we want to CHECK the access, but not do it).
Since canAccess returned true, findMethod() will still return the method from
the un-exported module. This leads to the second warning.
With --illegal-access=deny, the new canAccess()-check will return false and not
log anything.
Then findMethod() will search further for an exported method.
I don't think there is anything more than can be done here.
The warnings will persist, but they will never turn into errors. And that is
the primary goal.
(Maybe there should be some hint in the documentation about this to avoid
further bug tickets)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
