We saw the same issue here (two Class-Path entries).

But if we set <addClasspath> to false and put all the known classpath there, we can generate one Class-Path entry - not a pretty solution through.

Anybody over there has other workaround for this issue(I believe it is a bug)?

Thanks,

George



From: "Wayne Fay" <[EMAIL PROTECTED]>
Reply-To: "Maven Users List" <users@maven.apache.org>
To: "Maven Users List" <users@maven.apache.org>
Subject: Re: classpath in jar manifest
Date: Tue, 9 May 2006 09:37:02 -0500

Sounds like a possible bug in the handling of Class-Path manifest
entry. I'd take a look at the source code for maven-jar-plugin and see
if you can't track it down.

Or file a JIRA bug and wait for someone to fix it for you.

Wayne

On 5/9/06, Fredrik Vraalsen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm moving a project from maven 1.1 to 2.0, but I've hit a problem with
> specifying the classpath in the manifest file in my main application jar
> and was wondering if someone here could help.
>
> Basically, I wish to add some resource directories to the classpath, in
> addition to the jar dependencies.  The reason why I cannot put the
> resources in a jar is that they are being read by the JDIC web browser
> component (https://jdic.dev.java.net/) - in effect Mozilla or IE, which
> do not understand jar files. ;-)
>
> In maven 1.1, I was able to do this with the following in
> project.properties:
>
>      maven.jar.manifest.classpath.add=true
>      maven.jar.classpath=help/ resources/
>
> This would create a single Class-Path: entry in the manifest file.
>
> I've been reading
> http://maven.apache.org/guides/mini/guide-manifest.html and have tried
>
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-jar-plugin</artifactId>
>    <configuration>
>      <archive>
>        <manifest>
>          <mainClass>splash.Splasher</mainClass>
>          <addClasspath>true</addClasspath>
>        </manifest>
>        <manifestEntries>
>          <Class-Path>help/ resources/</Class-Path>
>        </manifestEntries>
>      </archive>
>    </configuration>
> </plugin>
>
> However, this ends up creating _two_ Class-Path: entries in the manifest
> file, which is not allowed.
>
> Is there a way to get this to work in maven 2.0?  I'm using maven 2.0.4.
>
>
> Best regards,
>
> Fredrik Vraalsen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to