ctubbsii commented on PR #92: URL: https://github.com/apache/maven-apache-parent/pull/92#issuecomment-1555989215
> For me the decision whether a plugin should be loaded with or without extensions should primarily be driven by the plugin developer (not by the consumer). I agree. > The fact that this needs to be specified during loading and is not yet given by the plugin descriptor I consider a flaw in the design. I agree with that, too. > Do you have a use case where it makes sense that a plugin is loaded without extensions although it provides one? Not off hand, but if it's configurable by a user, I imagine that there's use cases where a plugin's execution is functionally altered by that configuration. Otherwise, why is this even made available for configuration by users? So long as it's configurable by users, I just seems sensible that configuration should be determined by the user in their `<build><plugins>` section and not in the parent POM's `<build><pluginManagement><plugins>` section. But, as I said originally, I don't really understand the need for this flag at all. Right now, my understanding is that it doesn't really do anything. So I'm not even sure why it's being added. -- 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]
