maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat
Date Wed, 20 Jul 2016 20:27:20 GMT

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

Robert Scholte commented on MNG-5995:
-------------------------------------

Just removing the dependencies from the pom.xml is not enough. With only these changes Maven
is broken, you can't build any Maven project anymore.

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

Mime
View raw message