[
https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394389#comment-15394389
]
ASF GitHub Bot commented on MNG-5995:
-------------------------------------
Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/89
Hi Karl
With my recent change, I compiled with an example project and I didn't have
any issues. This is what I did as per the Jira task description:
`mvn
-DdistributionTargetFolder=/Users/rajivpjs/Desktop/Apache/Maven/rajivpjs/maven/mavenfixtarget
clean package`
From the mavenfixtarget directory I ran:
`mvn -f /path/to/pom.xml clean package`
This gave me a BUILD SUCCESS.
I then removed the from the /lib/maven-compat-3.4.0-SNAPSHOT.jar and then
ran:
`mvn -f /patj/to/pom.xml validate`
The output was BUILD SUCCESS.
Have I missed anything?
> 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)
