You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2022/01/25 12:53:31 UTC

[GitHub] [maven-apache-parent] ctubbsii commented on pull request #63: [MPOM-288] - Update m-plugin-p to 3.6.4

ctubbsii commented on pull request #63:
URL: https://github.com/apache/maven-apache-parent/pull/63#issuecomment-1021154511


   @slawekjaranowski wrote:
   > Currently we have also defined dependency management for it in maven-parent with provided scope
   > 
   > https://github.com/apache/maven-parent/blob/master/pom.xml#L965-L970
   
   And, just as I said, people can't trust the convention breakage, so they override it anyway, making it redundant. Here's two examples:
   * https://github.com/apache/maven-compiler-plugin/blob/master/pom.xml#L103
   * https://github.com/apache/maven-clean-plugin/blob/master/pom.xml#L92
   
   While I wouldn't recommend breaking conventions in `maven-plugins` parent POM either, it is at least limited to the Apache Maven plugin developers in that POM. If its scope were managed in this POM, it would break conventions for much wider set of projects across the ASF, and even projects outside the ASF.


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org