[ http://jira.codehaus.org/browse/MNG-2284?page=comments#action_69265 ] 

Fredrik Vraalsen commented on MNG-2284:
---------------------------------------

Hi,

I'm still having problems with this, but of a different sort now.  If I have a 
configuration such as the following:

        <manifest>
                <addClasspath>true</addClasspath>
        </manifest>
        <manifestEntries>
                <Class-Path>resources/</Class-Path>
        </manifestEntries>

I now get the following in my manifest.mf:

Class-Path: resources/
Class-Path: resources/

In other words, still two Class-Path entries in the manifest file, only this 
time they both have the value 'resources/', and the classpath created by 
addClasspath is gone.  This is with latest maven-jar-plugin 2.1-SNAPSHOT 
(maven-archiver 2.1).

I'm trying to create a JUnit test-case for maven-archiver, but I'm still trying 
to work out the details of how to set this up. ;-)  In the meanwhile, I'll 
attach a simple stand-alone pom file which shows the problem.

> 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

Reply via email to