gnodet opened a new pull request, #12454:
URL: https://github.com/apache/maven/pull/12454

   ## Summary
   
   - Adds a new `RepositoryHttpsUpgradeStrategy` that automatically converts 
`http://` repository URLs to `https://` in POM files
   - Since Maven 3.8.1+, HTTP repositories are blocked by the 
`maven-default-http-blocker` mirror, so any `http://` repository URL causes 
build failures
   - Well-known repositories (Apache snapshots/releases, Maven Central variants 
like `repo1.maven.org`, `central.maven.org`) are mapped to their canonical 
HTTPS equivalents
   - All other `http://` URLs get a generic scheme upgrade to `https://`
   
   ## Sections handled
   
   - `<repositories>/<repository>` URLs
   - `<pluginRepositories>/<pluginRepository>` URLs
   - `<distributionManagement>/<repository>` and `<snapshotRepository>` URLs
   - Profile-scoped repositories in all of the above sections
   
   ## Test plan
   
   - [x] Well-known Apache repository URL normalization (snapshots, releases) — 
2 tests
   - [x] Maven Central variant normalization (repo1, central, 
repo.maven.apache.org) — 3 tests
   - [x] Trailing slash preservation for well-known URLs — 1 test
   - [x] Unknown URL returns null from mapping — 1 test
   - [x] Generic http→https conversion — 2 tests
   - [x] URLs already using https (no change) — 1 test
   - [x] POM with no repositories (no change) — 1 test
   - [x] Plugin repository URL upgrade — 1 test
   - [x] distributionManagement repository and snapshotRepository — 3 tests
   - [x] Profile-scoped repositories and pluginRepositories — 2 tests
   - [x] Multiple repositories in a single POM — 2 tests
   - [x] Repositories across all sections simultaneously — 1 test
   - [x] Edge cases (no URL element, no id element, central.maven.org 
normalization) — 3 tests
   - [x] Applicability tests (--model, --all, default, --model=false) — 4 tests
   - [x] All 495 existing tests pass
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to