You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rajiv Jain (JIRA)" <ji...@apache.org> on 2016/07/20 18:16:20 UTC
[jira] [Commented] (MNG-5995) Maven itself cannot run without
maven-compat
[ https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386356#comment-15386356 ]
Rajiv Jain commented on MNG-5995:
---------------------------------
I am currently working on this ticket.
Should the maven-compat component be removed too?
Thanks.
> 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
> Priority: Critical
>
> 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}
> No implementation for org.apache.maven.repository.RepositorySystem was bound.
> {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
(v6.3.4#6332)