Francois Armand created MASSEMBLY-883:
-----------------------------------------

             Summary: Transitive dependencies with scope provided are included 
with jar-with-dependencies descriptor
                 Key: MASSEMBLY-883
                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-883
             Project: Maven Assembly Plugin
          Issue Type: Bug
          Components: predefined descriptors
    Affects Versions: 3.1.0
            Reporter: Francois Armand


In the following case as shown by {{mvn dependency:tree}}{{, with the 
predifined descriptor `jar-with-dependencies`:}}
 
{{[INFO] +- com.jayway.jsonpath:json-path:jar:2.2.0:compile }}
{{[INFO] | +- net.minidev:json-smart:jar:2.2.1:compile }}
{{[INFO] | | \- net.minidev:accessors-smart:jar:1.1:compile }}
{{[INFO] | \- org.slf4j:slf4j-api:jar:1.7.16:provided}}
 

{{json-path}}, {{json-smart}}, {{accessors-smart }}are included, as expected.  

{{But }}{{slf4j-api}} is also included in the resulting jar.

Other direct dependencies with scope `provided` are correctly excluded from the 
final jar.

If this is the intendented behavior, which is highly surprising, could you 
document it in the corresponding descriptor documentation 
([http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies).]
 Could you also explain what descriptor would allow to achieve the desired 
behavior (or point to a resource explaining it, I wasn't able to find one).

Thanks.
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to