[ 
https://issues.apache.org/jira/browse/MASSEMBLY-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 
> <addClasspath>true</addClasspath> 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)

Reply via email to