Seems like you are using a fat jar( jar files within a jar file) I suspect this
error has something to do with winpack-3.6.jar. This jar contains windows
specific code, so not sure how it will run on a linux OS.
The reason for the error on Windows7 could be 32 bit vs 64 bit incompatibility.
I
It appears to be nothing obvious, then :) Sorry I wasn't much help.
On Wed, Mar 27, 2013 at 11:03 PM, Marc Benstein wrote:
> Joe, there is nothing screwy in the manifest. As I said, the jar works
> fine from Java 6 and 7. Also note, the exact build is used with Ant
> 1.8.4 and everything works g
Joe, there is nothing screwy in the manifest. As I said, the jar works
fine from Java 6 and 7. Also note, the exact build is used with Ant
1.8.4 and everything works great there. Anyways, here's the manifest.
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.0
Created-By: 1.7.0_17-b02 (Oracle Corp
Interesting. Is the manifest intact? Maybe post the contents of your
MANIFEST.MF from the generated JAR file, and perhaps there will be
something screwy in there.
On Wed, Mar 27, 2013 at 10:43 PM, Marc Benstein wrote:
> Joe, there is not an error when I try jar tf myjar.jar. I see the
> contents
Joe, there is not an error when I try jar tf myjar.jar. I see the
contents just fine.
On Wed, 2013-03-27 at 19:56 -0600, Joe Attardi wrote:
> Is the error just when you try to execute the JAR? What if you simply try
> to list its contents (jar tf myjar.jar)?
>
>
> On Wed, Mar 27, 2013 at 8:27 PM,
Is the error just when you try to execute the JAR? What if you simply try
to list its contents (jar tf myjar.jar)?
On Wed, Mar 27, 2013 at 8:27 PM, Marc Benstein wrote:
> Howdy,
>
> Java 5 fails to execute jars created with Ant 1.9.0. Java 6 and 7 work
> fine to execute the jar.
>
> The message
Howdy,
Java 5 fails to execute jars created with Ant 1.9.0. Java 6 and 7 work
fine to execute the jar.
The message I am seeing in Java 5 is "Invalid or corrupt jarfile"
I have tried my target JVM of 1.5.0_06 on Windows 7 and Linux and I get
the same output. I have also tried 1.5.0_22 with the sa
Ok, I think I've found my problem. The fact is the system classloader
is never updated, but the context classloader is. So, all I have to do
is to substitute any instance of
ClassLoader cl = ClassLoader.getSystemClassLoader();
with
ClassLoader cl = Thread.currentThread().getContextClassL
On Tue, Mar 26, 2013 at 11:43 PM, Rainer Noack wrote:
> if you're launching ant via shell script, it is using
> oata.launcher.Launcher.java
>
> This class reorganises the classpath a bit.
[...]
Hi Rainer,
then how can I pass to the new ClassLoader a custom classpath? (which
is in fact the path(
