gnodet opened a new issue, #12570: URL: https://github.com/apache/maven/issues/12570
## Context PR #12332 added the `executable()` function for conditional profile activation (MNG-8768). During review, it was identified that `executable()` conditions survive into published consumer POMs via `DefaultConsumerPomBuilder`, which means: - A consumer pulling the POM from a repository will silently evaluate the `executable()` condition against their own `PATH` - Two developers building the same project can get different effective models depending on installed tools - The model validator warning added in #12332 only fires for the POM author, not downstream consumers ## Proposal Strip `executable()` conditions from consumer POMs during `DefaultConsumerPomBuilder` processing, similar to how `<build>` sections are stripped from profiles. This ensures the function remains useful for local build decisions without polluting published artifacts. ## References - PR #12332: https://github.com/apache/maven/pull/12332 - Original issue: MNG-8768 / #10115 - Review discussion: https://github.com/apache/maven/pull/12332#pullrequestreview-2989569503 - Contributor agreed to tackle this as a follow-up: https://github.com/apache/maven/pull/12332#issuecomment-4776264584 -- 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]
