slachiewicz opened a new pull request, #12948: URL: https://github.com/apache/maven/pull/12948
A model resolved from a repository should contribute less to the build than the project's own POM. These commits make that consistent across the model builder. - **Repository precedence.** Repositories contributed by a resolved model merge recessively; those supplied by the request or session keep precedence. `BUILD_*` requests — the project being built — are unaffected. - **Property interpolation.** Models built while resolving a dependency POM or its parents interpolate against a small environment-independent allowlist (`java.*`, `os.*`, `maven.*`, separators, and the CI-friendly `revision`/`changelist`/`sha1`). Everything else is left as a literal expression. `maven.model.dependencyInterpolation.full` restores the previous behaviour. - **Profile activation.** For the same models, profiles activated by `file`, `property` or `condition` are skipped, and profiles that do activate contribute no repositories. Settings and CLI profiles are untouched. - **Parent cache partitioning.** The resolved-parent cache is keyed by resolution origin, so a parent reached from a dependency chain and the same parent reached from the project's own chain no longer share an entry. - **Imported dependency management.** Dependency management imported from a repository-resolved POM may not declare `system` scope or a `systemPath`; such entries are dropped with a warning. `maven.repository.dependencyManagement.allowSystemScope` restores the previous behaviour. Imports resolved from the reactor are unaffected. Each change is a separate commit. -- 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]
