[
https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15396328#comment-15396328
]
ASF GitHub Bot commented on MNG-5995:
-------------------------------------
Github user rajivpjs commented on the issue:
https://github.com/apache/maven/pull/89
You are right. I tried
`/Users/rajivpjs/Desktop/Apache/Maven/rajivpjs/maven/mavenfixtarget/bin/mvn -f
/path/to/pom.xml clean package -V`
It shows version 3.3.9.
Maybe you are right, this issue might be hard for me to fix right now. So,
I will close this pull request soon. By the way if you don't mind me asking did
you guess me having 3.3.9 or you saw it in some output in my logs? I can't see
where you find out that information. Having look at the output I have posted, I
don't see anything with 3.3.9.
> 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)
