-
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
bootstrap bits use old version of jsoup when outside quarkus build, platform bom manages old version #21402
Labels
kind/bug
Something isn't working
Milestone
Comments
Tree from bootstrap-core to jsoup
|
Thanks @aloubyansky, change looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
#19590 updated the jsoup version in the build-parent after dependabot (and now various other scans) flagged it. The version property sits in a group commented "Align various dependencies that are not really part of the bom".
The bootstrap bits do have a transitive dependency on jsoup however, via the maven resolver and its use of wagon-http. So the build-parent manages the version to the new one during the quarkus build and testing, but then users of quarkus will likely use a different version since it isnt managed.
Also, unlike the core, the platform bom does actually manage the jsoup version, but still to the older one, so anything using that may then actually also actually be getting managed to use the old version specifically.
From https://issues.apache.org/jira/browse/WAGON-612 it doesnt seem like its considered an issue or priority for wagon-http itself, but that isnt to say having that version there wont present folks issues for other areas.
Either way certainly it would be nice if the platform bom wasnt managing the version to the old one which causes warnings, and if the quarkus build was testing things with a version users will likely actually get.
Should/could the bootstrap bom be managing this?
Expected behavior
Same, newer, version of dependency used during quarkus build and by eventual users.
Actual behavior
Most likely different versions used unwittingly, managed or unmanaged, causing warnings during dependency scans.
The text was updated successfully, but these errors were encountered: