Well... This is weird...
I was generating an index.list file in my jar using
true
When I removed that, all my problems with the external manifest went away...
It looks like there is some kind of problem with the index element and using
an external manifest.
My thanks to those who replied in an
> From: wayne...@gmail.com
> Date: Thu, 9 Jan 2014 13:06:10 -0600
> Subject: Re: Can't set Class-Path in jar using external manifest file
> To: users@maven.apache.org
>
> > I have tried Java 1.6.0_32 and 1.7.0_09. They both behave the same.
>
> Try this:
> cr
> I have tried Java 1.6.0_32 and 1.7.0_09. They both behave the same.
Try this:
create a jar file that you know works with Maven
test to be sure it works
unzip the file
edit the file by hand to swap those 2 lines
zip the file back up, rename to .jar etc
test with JVM
Just remove Maven entirely f
I compared the files using WinMerge.
I have tried Java 1.6.0_32 and 1.7.0_09. They both behave the same.
Earl
--
View this message in context:
http://maven.40175.n5.nabble.com/Can-t-set-Class-Path-in-jar-using-external-manifest-file-tp5781041p5781045.html
Sent from the Maven - Users mailing
> I exported the manifest from the non-working jar file to a second file. I
> then compared the two files. The files are identical except for the position
> of the Built-By and Build-Jdk elements. In the maven generated manifest,
...
> The Class-Path elements themselves are identical!!
How did yo
I've been going around and around with this one for a few hours now.
I am using Maven 3.1.1
I created a jar file, and had the maven-jar-plugin generate the manifest
file with the classPath for me. I am then able to sucessfully execute the
jar file with java -jar.
I then exported the manifest fro
