[
http://jira.codehaus.org/browse/MSHARED-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luberto Klaassen updated MSHARED-168:
-------------------------------------
Attachment: maven-archiver-test.zip
To illustrate the problem I created a very simple multimodule project with a
main-jar module that has a dependency on both a referenced-jar and a
referenced-rar module. When I run a 'mvn install' and inspect the MANIFEST.MF
of the generated main-jar.jar module, the Class-path only contains the
referenced-jar.jar and not the referenced-rar.rar. I really need this rar
dependency added to the classpath for my project, because without it my
solution doesn't work.
> addClasspath doesn't add dependencies to RAR artifacts
> ------------------------------------------------------
>
> Key: MSHARED-168
> URL: http://jira.codehaus.org/browse/MSHARED-168
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4.1
> Reporter: Luberto Klaassen
> Priority: Blocker
> Attachments: maven-archiver-test.zip
>
>
> When using the maven-jar-plugin to create a JAR for an artifact, the
> dependencies to RAR artifacts aren't added to the Class-path of the
> MANIFEST.MF when the addClasspath parameter is set to true.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
