Update OIDCng to multi-Maven-module structure#242
Merged
oharsta merged 2 commits intoOpenConext:mainfrom Mar 21, 2025
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #242 +/- ##
=======================================
Coverage ? 90.06%
Complexity ? 654
=======================================
Files ? 85
Lines ? 2385
Branches ? 268
=======================================
Hits ? 2148
Misses ? 126
Partials ? 111 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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 PR proposes a multi-module Maven structure for OIDCng. This structure allows for the addition of a release module which can be used to prepare release packages which includes (sample) configuration. As part of the restructuring, all version numbers have been moved to the parent POM. Also, where applicable, version numbers have now been pointed to the BOM of Spring Boot itself.