Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Blocker
-
Resolution: Unresolved
-
Affects Version/s: maven-archiver-2.4.1
-
Fix Version/s: None
-
Component/s: maven-archiver
-
Labels:None
-
Number of attachments :
Description
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.
Issue Links
- is related to
-
MNG-3497
rar, par and ejb3 archives should not be added to classpath
-
Activity
Luberto Klaassen
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Attachment | maven-archiver-test.zip [ 51772 ] |
Benjamin Bentmann
made changes -
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.