maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat
Date Sat, 13 Oct 2018 17:25:00 GMT

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

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

hboutemy commented on a change in pull request #185: [MNG-5995] Remove dependency to maven-compat
URL: https://github.com/apache/maven/pull/185#discussion_r224966165
 
 

 ##########
 File path: pom.xml
 ##########
 @@ -545,6 +545,12 @@ under the License.
             </lifecycleMappingMetadata>
           </configuration>
         </plugin>
+        <!-- use 3.x version. Replace with final version -->
 
 Review comment:
   why upgrading this plugin? this is not related to avoiding core requiring maven-compat,
isn't it?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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.x-candidate
>
>
> 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