gnodet commented on issue #13100: URL: https://github.com/apache/maven/issues/13100#issuecomment-5664058894
For the record: the activation axis (#13084) has a fix in progress at #13112 that takes the principled approach — sandbox the `ProfileActivationContext` rather than filter by activation type. The short version of what #13112 does: - **File activation** → suppressed (publisher paths don't exist on the consumer machine) - **User property activation** (consumer `-D` flags) → suppressed (consumer didn't set those for the dependency) - **System property activation** (`java.version`, `os.name`, …) → preserved (platform facts) - **POM-declared `<properties>` activation** → preserved (part of the artifact's published identity — this is the case #13095 missed) - **JDK / OS / `activeByDefault`** → preserved (always correct) This supersedes #13095. It will need a backport to `maven-3.10.x`. --- The repository-stripping axis (your original concern, and the new comment about alternating `public`/`inhouse` profiles each declaring their own repositories) is a separate question that #13112 deliberately doesn't touch. The redefine-detection framing — honor declared repos, warn/fail on redefinition of existing ones (especially `central`) — looks like the right approach. That's a separate PR/discussion when the design is settled. -- 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]
