Details
-
Bug
-
Status: Reopened
-
Critical
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Due to a bug in the Maven resolver, plugin and core extensions were resolved incorrectly: the direct test and provided dependencies were ignored.
Ironically, this fix breaks some plugins because direct test dependencies now take precedence over transitive compile one: see MNG-5739
(we know only one case where provided case has an impact: MPLUGIN-296, and in this only case, the new behaviour is more consistent than the previous)
Attachments
Attachments
Issue Links
- breaks
-
MEAR-246 Upgrade the EAR lifecycle to use the maven-resources-plugin 3.0.2.
- Closed
-
MPLUGIN-296 java.lang.ClassNotFoundException: org.apache.maven.plugins.annotations.Execute
- Closed
-
MWAR-400 Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2
- Closed
-
MRESOURCES-234 Upgrade of commons-io to 2.5 and correction of invalid scope.
- Closed
-
MPMD-230 Required class missing: org/apache/commons/io/IOUtils
- Closed
- is blocked by
-
MRESOLVER-8 ScopeDependencySelector incorrectly de-selects direct dependencies
- Reopened
-
MRESOLVER-9 DefaultDependencyCollector does not correctly handle dependency management
- Reopened
-
MRESOLVER-10 New 'TransitiveDependencyManager' supporting transitive dependency management
- Closed
- is related to
-
MPLUGIN-321 improve documentation on maven-plugin-annotations telling that optional=true is sufficient
- Closed
- relates to
-
MNG-5739 Adding a test dependency can move dependencies from the compile scope to the test scope
- Open
- mentioned in
-
Page Loading...