maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat
Date Sun, 03 Mar 2019 12:23:02 GMT

    [ https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782702#comment-16782702
] 

Hudson commented on MNG-5995:
-----------------------------

Build succeeded in Jenkins: Maven TLP » maven » MNG-6294 #12

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6294/12/

> 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 &amp; Build, core
>    Affects Versions: 3.3.9
>            Reporter: Robert Scholte
>            Assignee: Sylwester Lachiewicz
>            Priority: Critical
>             Fix For: 3.6.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)

Mime
View raw message