[MPLUGIN-370] check that plugin dependencies that are already exported by Maven are scope provided

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.6.0
• Fix Version/s: 3.6.2
• Assignee: Tamas Cservenak
• Reporter: Herve Boutemy
• Created: 21/Feb/21 18:30
• Updated: 29/May/24 11:38
• Resolved: 21/Oct/21 18:44

Description

see MNG-7097: Maven 4 will optimize downloads even when these dependencies are not with provided scope

but for older Maven versions, marking the dependencies provided remains useful: if maven-plugin-plugin helps do the configuration, it will be easier

Issue Links

• is related to: MPLUGIN-446 ERROR during build of m-plugin-report-p and m-plugin-p: Dependencies in wrong scope
• is related to: MPLUGIN-385 Clarify usage of scope "provided" for Maven artifacts with group id "org.apache.maven"
• is related to: SLING-12331 Update sling maven plugins to maven 3.8.x
• is related to: JCRVLT-586 Mark Maven-exported dependencies as scope provided
• is related to: MSITE-870 Mark Maven-exported dependencies as scope provided
• is related to: MNG-7097 Plugin Dependency Resolution: don't download Maven-provided artifacts
• links to: GitHub Pull Request #38