You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/12/29 22:30:00 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=16730843#comment-16730843 ]
Michael Osipov commented on MNG-5995:
-------------------------------------
[~slachiewicz], as far as I understand your GH comments, this requires work in other components and cannot be fixed in 3.6.1? Can it? Maybe 3.7.0?
> 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)