[ http://jira.codehaus.org/browse/MNG-2284?page=all ]
Mike Perham closed MNG-2284:
----------------------------
Assign To: Mike Perham
Resolution: Fixed
Patch applied with small tweaks (the user supplied value should come first so
its resources can come first in the classpath and override resources in the
standard jars). maven-archiver is no longer part of Maven, proper, so the fix
version is irrelevant. It is fixed in maven-archiver 2.1 which will be part of
the maven-jar-plugin 2.1 release.
> Cannot specify additional classpath entries in manifest when using
> addClasspath
> -------------------------------------------------------------------------------
>
> Key: MNG-2284
> URL: http://jira.codehaus.org/browse/MNG-2284
> Project: Maven 2
> Type: Bug
> Components: maven-archiver
> Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4
> Environment: Maven 2.0.4, maven-jar-plugin 2.0 and 2.1-SNAPSHOT, JDK
> 1.5.0_06, Windows XP
> Reporter: Fredrik Vraalsen
> Assignee: Mike Perham
> Fix For: 2.0.5
> Attachments: MNG-archiver-classpath.patch
>
>
> When using addClasspath, e.g. in the maven-jar-plugin, it is not possible to
> add additional classpath entries using manifestEntries, as this generates an
> illegal manifest file (contains two Class-Path entries). Please see
> http://jira.codehaus.org/browse/MJAR-41
> I have been looking through the code, and it seems this might need to be
> resolved in MavenArchiver? I've attached a simple fix that solves the
> problem for me, but a more thorough solution might be needed of course. ;-)
--
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
