I started asking this on the user list, but no response, and it seems deeper
than just incorrect usage. Apologies if that's what it turns out to be.
I've broken it down into a very basic build.xml and single source code file.
The build.xml has a single target to unzip, and run javadoc. I've attached a
bz2 archive of the build.xml, the source file, and a -debug log of using the
unzip task and relying on the src.zip having been expanded with the native OS
unzip command before running. The single source code file implements the
javax.naming.Context interface. When run as-is (build-internal-unzip.log) the
javadocs do not inherit from javax.naming.Context. If you comment out lines 6
and 7 from build.xml and run 'unzip -d jdk ${JAVA_HOME}/src.zip' and then build
(build-external-unzip.log) the javadocs do inherit from javax.naming.Context.
I've tried using 'jar xvf ${JAVA_HOME}/src.zip' and that has the same result as
using the <unzip> task. The javax/naming/Context.java file is the same
(compared MD5 checksums) no matter how I uncompress src.zip.
-----Original Message-----
From: Justin Georgeson
Sent: Friday, November 04, 2011 2:21 PM
To: [email protected]
Subject: RE: difference between unzip task and unzip executable
Just to eliminate any possibility of file handle closure, disk I/O flushing,
etc. I put the <unzip> in a separate target that only does the unzip, ran that
target by itself, and then ran ant a second time for the javadoc target and it
still fails. I don't understand what the problem can be when everything says
the contents of the files are identical. Even if I use the <unzip> task to put
the contents of src.zip in the 'src' folder that my source code is in, there's
no javadoc inheritance.
-----Original Message-----
From: Justin Georgeson [mailto:[email protected]]
Sent: Friday, November 04, 2011 1:35 PM
To: [email protected]
Subject: difference between unzip task and unzip executable
I'm trying to get javadoc inheritance working from JDK classes, and what I'm
finding is if I use
<unzip src="${env.JAVA_HOME}/src.zip dest="${env.BUILD_DIR}/docs/jdk"/>
in my Ant target, the javadoc task ignores that sourcepath entry because it
doesn't contain any packages matching my packagenames parameter (running with
-verbose says it "doesn't contain any packages, dropping it"). If I run 'unzip
-d ${BUILD_DIR}/docs/jdk ${JAVA_HOME}/src.zip' in the shell before running Ant
(and the target just assumes the folder is there) everything works right. I've
run a 'diff -qr' on the result of both unzip methods and no differences are
found, even 'rsync -acv' says they're the same
----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and
privileged information for the sole use of the intended recipient. Any review,
use, distribution, or disclosure by others is strictly prohibited. If you are
not the intended recipient (or authorized to receive information for the
intended recipient), please contact the sender by reply e-mail and delete all
copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
