[jira] [Commented] (MASSEMBLY-883) Transitive dependencies with scope provided are included with jar-with-dependencies descriptor

2018-04-16 Thread Francois Armand (JIRA) 

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16439439#comment-16439439
 ] 

Francois Armand commented on MASSEMBLY-883:
---

As explained here: 
[https://stackoverflow.com/questions/49784429/how-to-exclude-transitive-dependencies-with-scope-provided-with-maven-assembly-p]
 I believe it's a bug. I now use maven-shade-plugin whose behavior is ok.

> 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
>Priority: Major
>
> 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)

[jira] [Commented] (MASSEMBLY-883) Transitive dependencies with scope provided are included with jar-with-dependencies descriptor

2018-04-13 Thread Francois Armand (JIRA) 

[ 
https://issues.apache.org/jira/browse/MASSEMBLY-883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437486#comment-16437486
 ] 

Francois Armand commented on MASSEMBLY-883:
---

I added a minimal reproduction project here: 
https://github.com/fanf/test-maven-assembly/blob/master/readme.md

> 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
>Priority: Major
>
> 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)

[jira] [Updated] (MASSEMBLY-883) Transitive dependencies with scope provided are included with jar-with-dependencies descriptor

2018-04-11 Thread Francois Armand (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MASSEMBLY-883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francois Armand updated MASSEMBLY-883:
--
Description: 
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.
  

  was:
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.
 


> 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
>Priority: Major
>
> 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)

[jira] [Created] (MASSEMBLY-883) Transitive dependencies with scope provided are included with jar-with-dependencies descriptor

2018-04-11 Thread Francois Armand (JIRA) 
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)