[MNG-5995] Maven itself cannot run without maven-compat

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.3.9
• Fix Version/s: 3.6.1
• Component/s: Bootstrap & Build, Core
• Assignee: Sylwester Lachiewicz
• Reporter: Robert Scholte
• Created: 05/Apr/16 22:58
• Updated: 08/Jan/21 22:58
• Resolved: 26/Jan/19 19:04

Description

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:

[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

Reason: there's only one implementation: o.a.m.r.l.LegacyRepositorySystem, which is part of maven-compat.

Issue Links

• is related to: MNG-6642 Tycho-based modules do not build with 3.6.1 (works with 3.6.0)
• is related to: MNG-6561 New RepositorySystem implementation as replacement of deprecated from maven-compat
• relates to: MSITE-833 Remove dependency to maven-compat
• relates to: MNG-7071 Remove warning about ignored profiles.xml
• relates to: MRRESOURCES-92 Upgrade to Maven 3.0 compatiblity
• relates to: MENFORCER-267 Upgrade to make Maven 3.1+
• links to: GitHub Pull Request #185