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 14:05:55 UTC

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

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


   The scope should not be in MPOM.
   The MPOM has certain purpose to help and not to break via restrictions.
   Simply dependency management declares versions, the same with plugin management.
   Plugins section is different story.
   The way that we declare versions of dependencies has certain purpose - we prove that the JDK version and Maven API/versions and plugins development would be in consistent state. It's the developer's responsibility to say what dependency would be on certain type of classpath (compilation, test, runtime). The more restrictions of scope we provide in MPOM the more investigation time would be spent on finding out this root cause in MPOM.


-- 
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