What I wrote below is incorrect.
The problem is due to a difference between javac in jdk1.4 and jdk 1.5.
This can be seen on the command line:
[EMAIL PROTECTED]:~/tmp/test > export JAVA_HOME=/usr/java/j2sdk1.4.2
[EMAIL PROTECTED]:~/tmp/test > export PATH=$JAVA_HOME/bin:$PATH
[EMAIL PROTECTED]:~/t
Peter Reilly wrote:
This should be a FAQ!
You have a .class file in your class path (i.e. not a directory
or a .jar file). Starting with ant 1.6, ant will open the
files in the classpath checking for manifest entries. This attempted
opening
will fail with the error "java.util.zip.ZipException
This should be a FAQ!
You have a .class file in your class path (i.e. not a directory
or a .jar file). Starting with ant 1.6, ant will open the
files in the classpath checking for manifest entries. This attempted opening
will fail with the error "java.util.zip.ZipException"
The problem does not
On Tue, 7 Jun 2005, Fabricio M. Sanchez <[EMAIL PROTECTED]>
wrote:
> After deleting all classes and compiling using the javac task
> (target name is compile, see code below), I then compile the source
> again. The first time I compile (using 'ant compile')it builds
> successfully. When I compile
Don't know if this will help, but I've seen some strange exceptions
moving from jdk 1.4.x to 1.5.x if the JAVA_HOME env var doesn't point to
the same jdk version as the compiler used by the javac task. Make sure
things are in sync. If nothing else, it will rule this out as the cause.
Maury
Fab