Draft
Conversation
- Removed Gretty to get rid of vulnerable dependencies, use an embedded jetty 12 instance instead - Upgrade to Gradle 8.4 - Upgrade to Dependency Check 12.2.0 - Changed Copyright header check to support 2025 until 2029 (cherry picked from commit d532bbc) Co-authored-by: Chris Dennis <chris.w.dennis@gmail.com>
mathieucarbou-ibm
approved these changes
Apr 3, 2026
Member
|
@chrisdennis @chrisdennis @alexander-komarov-ibm : still some infra (I think) issues after Chris build improvements, |
aurbroszniowski
approved these changes
Apr 3, 2026
Contributor
aurbroszniowski
left a comment
There was a problem hiding this comment.
I checked the demos and they are working fine.
The Gradle part looks fine to me, but I’ll defer to you
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a combination of two things:
@mathieucarbou in principle you could use this PR to allow you to release 3.11... but I'm a little worried about doing that without taking more time to validate the fairly extensive changes I've had to make to the package plugin logic. The alternative is to pull out the dependency-check plugin entirely and move forward without it for now. That would be super simple, and probably much safer. I'll let you guys decide which way you want to go.
(cherry picked from commit d532bbc)