[GitHub] [hop] pscigala commented on pull request #1298: [HOP-3606] Disabled java 11 tests

[GitBox <gi...@apache.org>]

pscigala commented on pull request #1298:
URL: https://github.com/apache/hop/pull/1298#issuecomment-1023054821


   
   Seems that builds are failing because of an "An illegal reflective access" warnings.
   This is common case when using things like powermock and reflective manipulation libraries in java 11 and above.
   The question is - is it will be good enough to use "--illegal-access=permit/warn" flag in surefire plugin?
   Or should we rather try to find another way to solve the problem with mocking/reflective manipulation libraries (probably will require much more refactoring)?
   
   The first path could fit well in java-11 release. However, in java-17 the flag is removed and "--add-opens" seems to replace the behaviour but requires providing explicitly in argument which packages are opened for manipulation.
   
   Surprisingly at the moment "--illegal-access=permit" is used by surefire plugin in root pom.xml, but seems to not work for submodules during github build?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@hop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org