Max Schaefer created MASSEMBLY-751:
--------------------------------------
Summary: Transitive dependencies are not considered when scope is
explicitly overriden
Key: MASSEMBLY-751
URL: https://jira.codehaus.org/browse/MASSEMBLY-751
Project: Maven Assembly Plugin
Issue Type: Bug
Components: dependencySet
Affects Versions: 2.5.3
Environment: Java HotSpot(TM) 64-Bit Server VM warning: ignoring
option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T18:29:23+01:00)
Maven home: C:\Program Files\Apache Software Foundation\apache-maven-3
Java version: 1.8.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_25\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
Reporter: Max Schaefer
Attachments: test-assembly.zip
My project is configured to copy all jars including transitive dependencies.
My project has two dependencies, one scope compile other scope provided.
Both dependencies depend themselves on slf4j-log4j12, one scope compile other
scope provided.
As soon as I add slf4j-log4j12 to dependencyManagement of my project and
specify a scope then slf4j-log4j12 and it's transitive dependencies are not
copied anymore. If I remove the scope, slf4j-log4j12 and it's transitive
dependencies are copied.
Actually I expect the latter.
Run test project (clean package) and check dir
test-assembly\target\jars\test-assembly-1.0-SNAPSHOT\test-assembly-1.0-SNAPSHOT\runtime
Expected: 4 jars
Actual result: 1 jar
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
