[ https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734655#comment-16734655 ]
Robert Scholte commented on MNG-5995: ------------------------------------- Right, ideally maven-compat is not available on the classpath, unless a plugin explicitly requires it. Only in that case the maven-compat jar of the Maven Runtime should be added to the classpath (like now: the version of maven dependencies of the plugin doesn't have any effect, they are filtered out and the Maven Runtime dependencies are used). This is probably too complex is doesn't gain enough. However, we might hit similar issues with the next major version of Maven, but that's for later. > Maven itself cannot run without maven-compat > -------------------------------------------- > > Key: MNG-5995 > URL: https://issues.apache.org/jira/browse/MNG-5995 > Project: Maven > Issue Type: Bug > Components: Bootstrap & Build, core > Affects Versions: 3.3.9 > Reporter: Robert Scholte > Assignee: Sylwester Lachiewicz > Priority: Critical > Fix For: 3.6.1 > > > For all the 3.0 versions of the maven-plugins we require to not depend on > maven-compat anymore. However, the Maven distribution still requires > maven-compat. A simple proof: remove {{lib/maven-compat-3.x.y}} and execute > {{mvn validate}}. > You'll get the following exception: > {noformat}[WARNING] Error injecting: > org.apache.maven.project.DefaultProjectBuildingHelper > com.google.inject.ProvisionException: Unable to provision, see the following > errors: > 1) No implementation for org.apache.maven.repository.RepositorySystem was > bound. > while locating > org.apache.maven.project.DefaultProjectBuildingHelper{noformat} > Reason: there's only one implementation: o.a.m.r.l.LegacyRepositorySystem, > which is part of maven-compat. -- This message was sent by Atlassian JIRA (v7.6.3#76005)