-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to xstream 1.4.13 to reduce illegal reflective access warnings #11956
Conversation
/cc @geoand Not sure about backport to 1.7. Seems small enough... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about adding this to the BOM, I would prefer keeping it just as a dependency in the test
I must have misunderstood that comment in pom.xml. I though it was all about Optaplanner. |
I am pretty sure it does |
Fixes #10303 for some cases when using JUnit5 ParameterResolver. Includes x-stream/xstream#218 that tries to avoid such warnings at XStream creation time. Also adds xstream to dependabot. Comment regardings optaplanner was outdated.
I removed it from the BOM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks!
I don't think we need it 1.7, but we can always do it if necessary |
So this PR jobs we run around 7-8 hours back and my PR #11925 was merged 21 hours back. Yet this PR failed with the JDK 14 job getting cancelled for not being able to complete the DB2 container stop:
So it looks like my PR didn't really help in this case. I guess we might have to check with the plugin owners to understand what could be causing this. |
Fixes #10303 for some cases when using JUnit5 ParameterResolver.
Includes x-stream/xstream#218 that tries to avoid such warnings at XStream creation time.
Also adds xstream to dependabot. Comment regardings optaplanner was outdated.
It does remove the warnings in my current project but it really depends how on your parameter looks like internally (which results in different xstream converters being actually used).
A good example is
ParameterResolverTest
, before:after:
Trace (after):
This issue won't be solved entirely until xstream 1.5 (ETA is unknown).