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

ASF GitHub Bot commented on MNG-5995:
-------------------------------------

GitHub user rajivpjs opened a pull request:

    https://github.com/apache/maven/pull/89

    [MNG-5995] Removed maven-compat as it not required anymore for maven …

    Please review and let me know of any changes.
    
    Thanks.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rajivpjs/maven MNG-5995

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/maven/pull/89.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #89
    
----
commit 998ed3160d00d6c6d1a1a8bf16db55f6dcf36f4c
Author: Rajiv Jain <rajiv...@gmail.com>
Date:   2016-07-20T20:05:55Z

    [MNG-5995] Removed maven-compat as it not required anymore for maven 3.0 
versions

----


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

Reply via email to