[jira] [Commented] (MASSEMBLY-850) Class-path ignores runtime dependencies

2018-12-24 Thread Enrico Olivelli (JIRA)


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

Enrico Olivelli commented on MASSEMBLY-850:
---

[~ondrej@devterium.cz] do you have time to test current master in order to 
check if your case has been fixed ?

We are going to release a new version of the plugin, it would be great to see 
that you will be happy with this new version

> Class-path ignores runtime dependencies
> ---
>
> Key: MASSEMBLY-850
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-850
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Reporter: Ondrej Par
>Priority: Major
>
> I add runtime-scoped dependencies using custom assembly descriptor and use 
> true in POM. Runtime dependencies are correctly 
> added to the JAR, and classpath is added to the manifest, however, it only 
> contains compile-scoped dependencies.
> This worked correctly with maven 2 and assembly:attached goal.



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


[jira] [Commented] (MASSEMBLY-850) Class-path ignores runtime dependencies

2018-04-21 Thread Michael Osipov (JIRA)

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

Michael Osipov commented on MASSEMBLY-850:
--

[~ondrej@devterium.cz], can you confirm Leonid's observations?

> Class-path ignores runtime dependencies
> ---
>
> Key: MASSEMBLY-850
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-850
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Reporter: Ondrej Par
>Priority: Major
>
> I add runtime-scoped dependencies using custom assembly descriptor and use 
> true in POM. Runtime dependencies are correctly 
> added to the JAR, and classpath is added to the manifest, however, it only 
> contains compile-scoped dependencies.
> This worked correctly with maven 2 and assembly:attached goal.



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


[jira] [Commented] (MASSEMBLY-850) Class-path ignores runtime dependencies

2018-04-16 Thread Leonid Rozenblyum (JIRA)

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

Leonid Rozenblyum commented on MASSEMBLY-850:
-

The fix for MASSEMBLY-675 also fixed this ticket for me

> Class-path ignores runtime dependencies
> ---
>
> Key: MASSEMBLY-850
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-850
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Reporter: Ondrej Par
>Priority: Major
>
> I add runtime-scoped dependencies using custom assembly descriptor and use 
> true in POM. Runtime dependencies are correctly 
> added to the JAR, and classpath is added to the manifest, however, it only 
> contains compile-scoped dependencies.
> This worked correctly with maven 2 and assembly:attached goal.



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


[jira] [Commented] (MASSEMBLY-850) Class-path ignores runtime dependencies

2018-04-16 Thread Leonid Rozenblyum (JIRA)

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

Leonid Rozenblyum commented on MASSEMBLY-850:
-

It's a pretty annoying bug.

Is there any known workaround or possibility to force the maven-assembly-plugin 
use maven-jar-plugin generated manifest which is correctly including runtime 
dependencies?

> Class-path ignores runtime dependencies
> ---
>
> Key: MASSEMBLY-850
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-850
> Project: Maven Assembly Plugin
>  Issue Type: Bug
>Reporter: Ondrej Par
>Priority: Major
>
> I add runtime-scoped dependencies using custom assembly descriptor and use 
> true in POM. Runtime dependencies are correctly 
> added to the JAR, and classpath is added to the manifest, however, it only 
> contains compile-scoped dependencies.
> This worked correctly with maven 2 and assembly:attached goal.



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