[MENFORCER-385] Enforce that transitive provided dependencies are contained in the runtime Maven classpath

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: Standard Rules
• Assignee: Robert Scholte
• Reporter: Konrad Windszus
• Created: 21/May/21 15:04
• Updated: 02/Jun/22 11:15
• Resolved: 27/May/21 21:03

Description

All dependencies with provided scope are not transitively inherited. While this isn't a problem usually during compile time it is a problem for Maven plugins at run time, as they use the Maven dependency classpath also at run time (https://maven.apache.org/guides/mini/guide-maven-classloading.html#3-plugin-classloaders). At run time they fail if the transitive provided dependency has not been declared explicitly.

As manually specifying all transitive (but hidden) provided dependencies is a very error-prone process an enforcer rule for that would be highly beneficial. Especially as the transitive dependencies have to be rechecked once you upgrade to a newer version.

Example:

My Maven Plugin "A" -> 3rd Party Library "B" -> Provided Dependency "C"

As "B" uses "C" at run time it needs to be declared as dependency of "A" as well otherwise you might see  java.lang.ClassNotFoundException when executing Maven plugin "A".

Issue Links

• causes: SLING-11369 Provide Maven Enforcer rule which checks that provided dependencies are contained in the runtime Maven classpath
• is caused by: MNG-2205 "provided" scope dependencies must be transitive
• is related to: JCRVLT-394 Get rid of "provided" scope for FileVault dependencies
• links to: GitHub Pull Request #97