chore: regenerate NOTICE after parent v51#275
Merged
bjagg merged 1 commit intouPortal-Project:masterfrom May 3, 2026
Merged
Conversation
Problem: uPortal-Project#274 bumped the parent to v51 but didn't regenerate NOTICE. `mvn notice:check` now fails on master, which would block `release:prepare` for 2.4.1. Goal: align NOTICE with the actual deployed dep tree so notice:check passes during release:prepare. Changes: - regenerate NOTICE via `mvn notice:generate` against current deps; picks up Apache Commons Lang (lang3 transitive) and license-name normalization across several entries (Apache-2.0 vs older variants); rolls Logback EPL v1 -> v2 from parent v51. Notes: WebproxyPortlet has zero commons-lang source imports and no local pom dep on commons-lang, so the parent v51 bare bump in uPortal-Project#274 worked cleanly -- only the NOTICE was missed.
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
1 participant
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.
Follow-up to #274 — that PR bumped the parent to v51 but didn't regenerate NOTICE. `mvn notice:check` is failing on master, which would block `release:prepare` for 2.4.1.
This PR runs `mvn notice:generate` against the post-v51 dep tree. Net effect: license-name normalization across several entries (Apache-2.0 vs older variants), Apache Commons Lang (lang3 transitive) added, Logback EPL v1 -> v2 roll from parent v51.
WebproxyPortlet had no local source/pom usage of `commons-lang` so the bare Renovate v51 bump in #274 was actually clean — unlike Bookmarks/Calendar/Courses/News/JasigWidget where the source migration had to land alongside the parent bump. Only the NOTICE drift was missed.
Test plan