You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Enrico Olivelli (JIRA)" <ji...@apache.org> on 2018/12/24 10:15:00 UTC
[jira] [Commented] (MASSEMBLY-850) Class-path ignores runtime
dependencies
[ https://issues.apache.org/jira/browse/MASSEMBLY-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16728310#comment-16728310 ]
Enrico Olivelli commented on MASSEMBLY-850:
-------------------------------------------
[~ondrej.par@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 <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)