ctubbsii commented on PR #92: URL: https://github.com/apache/maven-apache-parent/pull/92#issuecomment-1553975711
> > I don't expect it to be responsible for execution decisions. > > The loading with extensions has no impact on goal execution. I wasn't referring to goal executions. I was referring to the explicit choice to execute whatever the `<extension />` is causing to be executed. If that element has any execution (or effect, if you prefer) whatsoever, then it is a choice being made on behalf of users. That's new. Currently the only choice being made for users is the version. This is the same reason I wouldn't put `<scope>test</scope>` on a dependency in `<dependencyManagement>` (because that forces users to explicitly specify `<scope>compile</scope>` to override, when that's usually understood to be the default). The scope should be declared where the plugin is executed, not where its version is being managed. It seems like a similar principle is applicable here. -- 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]
