You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Stefan Bodewig <bo...@bost.de> on 2000/10/19 17:15:46 UTC

[ANNOUNCE] Ant 1.2 release candidate 2

Due to some rather major changes today we provide another release
candidate to be found at
<http://jakarta.apache.org/builds/ant/release/v1.2rc/> the old
archives have been overwritten.

The major changes are 

(1) <ejbc> has been reverted to the old version (as of Ant 1.1) that
doesn't run in the same VM as Ant and doesn't know about jikes. There
have been problems with the custom classloader that couldn't be
resolved in time for the release of Ant 1.2.

(2) SYSTEM entities with file URIs are now handled by Ant instead of
the XML parser (to be exact Ant resolves the URI instead of the
parser). This needs extended testing.

The following bugs in Ant 1.2rc1 have been fixed:

* MacOS X is now considered UNiX with respect to <chmod>

* Ant can be installed in a directory containing spaces on Windows.

* javac will use the specified logfile even if running the modern
compiler.

* no more stack traces on compilation failures.

* several documentation updates.

Re: [ANNOUNCE] Ant 1.2 release candidate 2

Posted by Ken Wood <kw...@i2.com>.
I need to know more about 'jlink'.

I did the following experiment:

 unjar 3 different jars into a temp directory,
 then use 'jar' to make a new jar file, A.jar

 jlink the same 3 jars to make a new jar file, B.jar

Then, I did 

  jar -tf A.jar | sort > /tmp/A.lst
  jar -tf B.jar | sort > /tmp/B.lst

Then I diff'ed A.lst and B.lst. There were NUMEROUS
differences, too numerous to even try to list.

I would have thought the two would be the same...

Am I not understanding something about what jlink
is supposed to do?

-ken