Skip to content

chore: regenerate per-submodule NOTICE files for parent v51 + lang3#112

Merged
bjagg merged 1 commit into
uPortal-Project:masterfrom
bjagg:chore/regen-submodule-notices
May 3, 2026
Merged

chore: regenerate per-submodule NOTICE files for parent v51 + lang3#112
bjagg merged 1 commit into
uPortal-Project:masterfrom
bjagg:chore/regen-submodule-notices

Conversation

@bjagg
Copy link
Copy Markdown
Member

@bjagg bjagg commented May 3, 2026

Follow-up to #111 — that PR regenerated the root NOTICE for the parent v51 + commons-lang3 work, but missed the per-submodule NOTICEs. Running `mvn notice:check` on current master fails on `courses-portlet-api`, which would block `release:prepare` for 2.1.1.

This PR brings the three submodule NOTICEs in sync with their actual dep trees post-v51 (license-name normalization: "Apache Commons Lang under Apache-2.0" vs the older "Commons Lang under The Apache Software License, Version 2.0", same for Joda-Time and SLF4J).

Test plan

  • `mvn -B notice:check` passes on all 4 reactor modules locally
  • CI green
  • After merge: `mvn release:clean release:prepare release:perform` for 2.1.1

Problem: uPortal-Project#111 regenerated the root NOTICE for the parent v51 +
commons-lang -> commons-lang3 work but missed the per-submodule NOTICE
files. Running `mvn notice:check` on master fails on
courses-portlet-api with 'Existing NOTICE file ... doesn't match
expected NOTICE file', which would block `mvn release:prepare` for
2.1.1.

Goal: bring every reactor module's NOTICE in sync with its actual
dep tree so notice:check passes across the full reactor.

Changes:
- courses-portlet-api/NOTICE, courses-portlet-dao/NOTICE,
  courses-portlet-webapp/NOTICE: regenerated via `mvn notice:generate`
  to pick up the post-v51 license metadata (Apache Commons Lang
  under Apache-2.0; Joda-Time / SLF4J license-name normalization).
- Verified `mvn notice:check` is now green on all four reactor
  modules (root + 3 submodules).
@bjagg bjagg merged commit 6e36212 into uPortal-Project:master May 3, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant