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/13 17:40:55 UTC

[ANNOUNCE] Feature Freeze of Ant 1.2

The Ant developers announce a feature freeze for Ant 1.2.

Binary and source distributions of the first release candidate can be
found at <http://jakarta.apache.org/builds/ant/release/v1.2rc/>. We
don't plan to do any further release candidate builds before the final
release, please use the nightly builds to get the latest bug fixes.

optional.jar is not complete, some optional tasks are missing and
might be added later.

Please give this version a try, enjoy the new features and report bugs
and problems to one of the Ant mailing lists so that we can address
them before we get to a final release.

Have fun

        Stefan Bodewig


Re: Another Question about jlink

Posted by Ken Wood <kw...@i2.com>.
Duh, carelessness on my part....

Without LOOKING, I assumed that JDK's jar
would create a manifest with an entry
for each file that was 'jarred'. So,
I thought I'd be missing that info.
My fault for not looking first, because
I now see that the jar's manifest has
no such list of classes.....

Which then begs the question - what
is the performance delta if some
java code accesses classes via a jar, and
the jar does NOT have a manifest that lists
all the available classes, versus accessing
classes from a jar that DOES have an entry
for each class in the manifest???? Or is
there any difference? 

Also, anyone have any ideas on the problem
I reported with ONE jar file causing a
checksum error???

Stefan Bodewig wrote:
> 
> >>>>> "KW" == Ken Wood <kw...@i2.com> writes:
> 
>  KW> Including one is not an option, since the jars I want to merge
>  KW> come from a nighly build, the contents can change, so I want the
>  KW> manifest to be automatic.
> 
> But the one you get when you simply jar up your temp directory is
> always the sam, isn't it? Ant's default Manifest simply consists of
> 
> Manifest-Version: 1.0
> Created-By: Ant ANTVERSION
> 
> so it isn't any better than supplying one of your own, is it?
> 
> Stefan

Re: Another Question about jlink

Posted by Stefan Bodewig <bo...@bost.de>.
>>>>> "KW" == Ken Wood <kw...@i2.com> writes:

 KW> Including one is not an option, since the jars I want to merge
 KW> come from a nighly build, the contents can change, so I want the
 KW> manifest to be automatic.

But the one you get when you simply jar up your temp directory is
always the sam, isn't it? Ant's default Manifest simply consists of

Manifest-Version: 1.0
Created-By: Ant ANTVERSION

so it isn't any better than supplying one of your own, is it?

Stefan

Another Question about jlink

Posted by Ken Wood <kw...@i2.com>.
Forgive me if this has been covered.....

If I "unjar" a set of jars into a temp directory, then
delete the manifests, then "jar" the temp directory,
I have merged all these files, and I have a jar WITH
a manifest.

Now, if I merge the jars with jlink, there is now now
manifest. Which kinda ruins it, eh? Including one
is not an option, since the jars I want to merge come
from a nighly build, the contents can change, so I
want the manifest to be automatic. Using jar to create
the merged jars gives me that, but it's "uglier" having
a sequence of unjar commands followed by a "jar" command
than a single jlink command.....

Am I missing something?

-ken


Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Stefan Bodewig <bo...@bost.de>.
optional.jar has been updated to contain all optional tasks except the
ones for starbase and weblogic.

Stefan

Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Stefan Bodewig <bo...@bost.de>.
optional.jar has been updated to contain all optional tasks except the
ones for starbase and weblogic.

Stefan

Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Ken Wood <kw...@i2.com>.
I meant, would NOT be part of default.properties....
Gee, it's to early in the day....

Ken Wood wrote:
> 
> I didn't look. I assumed that OPTIONAL meant
> you didn't have to have them, which meant they
> would be part of default.properties...
> I guess I should look at default.properties...
> 
> Nico Seessle wrote:
> >
> > ----- Original Message -----
> > From: "Ken Wood" <kw...@i2.com>
> > To: <an...@jakarta.apache.org>
> > Sent: Sunday, October 15, 2000 12:35 AM
> > Subject: Re: [ANNOUNCE] Feature Freeze of Ant 1.2
> >
> > > A suggestion for documentation.
> > >
> > > At the beginning of each Optional Task section, document
> > > the taskdef required to use the optional task. For example, with
> > > jlink I had to make an educated guess that JlinkTask is what I
> > > wanted, versus "jlink" which was another class in the jlink
> > > package....
> > >
> >
> > Since all tasks which are in CVS are included in
> > org/apache/tools/ant/taskdefs/default.properties there should be no need to
> > do so (of course it wouldn't be wrong to document it, but you shouldn't need
> > to use taskdef for tasks included with the ant distribution) .
> >
> > Where did you get your Ant from?
> >
> > Nico

Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Ken Wood <kw...@i2.com>.
I didn't look. I assumed that OPTIONAL meant
you didn't have to have them, which meant they
would be part of default.properties...
I guess I should look at default.properties...

Nico Seessle wrote:
> 
> ----- Original Message -----
> From: "Ken Wood" <kw...@i2.com>
> To: <an...@jakarta.apache.org>
> Sent: Sunday, October 15, 2000 12:35 AM
> Subject: Re: [ANNOUNCE] Feature Freeze of Ant 1.2
> 
> > A suggestion for documentation.
> >
> > At the beginning of each Optional Task section, document
> > the taskdef required to use the optional task. For example, with
> > jlink I had to make an educated guess that JlinkTask is what I
> > wanted, versus "jlink" which was another class in the jlink
> > package....
> >
> 
> Since all tasks which are in CVS are included in
> org/apache/tools/ant/taskdefs/default.properties there should be no need to
> do so (of course it wouldn't be wrong to document it, but you shouldn't need
> to use taskdef for tasks included with the ant distribution) .
> 
> Where did you get your Ant from?
> 
> Nico

Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Nico Seessle <Ni...@epost.de>.
----- Original Message -----
From: "Ken Wood" <kw...@i2.com>
To: <an...@jakarta.apache.org>
Sent: Sunday, October 15, 2000 12:35 AM
Subject: Re: [ANNOUNCE] Feature Freeze of Ant 1.2


> A suggestion for documentation.
>
> At the beginning of each Optional Task section, document
> the taskdef required to use the optional task. For example, with
> jlink I had to make an educated guess that JlinkTask is what I
> wanted, versus "jlink" which was another class in the jlink
> package....
>

Since all tasks which are in CVS are included in
org/apache/tools/ant/taskdefs/default.properties there should be no need to
do so (of course it wouldn't be wrong to document it, but you shouldn't need
to use taskdef for tasks included with the ant distribution) .

Where did you get your Ant from?

Nico



Re: [ANNOUNCE] Feature Freeze of Ant 1.2

Posted by Ken Wood <kw...@i2.com>.
A suggestion for documentation.

At the beginning of each Optional Task section, document
the taskdef required to use the optional task. For example, with
jlink I had to make an educated guess that JlinkTask is what I
wanted, versus "jlink" which was another class in the jlink
package....

At 05:40 PM 10/13/00 +0200, you wrote:
>The Ant developers announce a feature freeze for Ant 1.2.
>
>Binary and source distributions of the first release candidate can be
>found at <http://jakarta.apache.org/builds/ant/release/v1.2rc/>. We
>don't plan to do any further release candidate builds before the final
>release, please use the nightly builds to get the latest bug fixes.
>
>optional.jar is not complete, some optional tasks are missing and
>might be added later.
>
>Please give this version a try, enjoy the new features and report bugs
>and problems to one of the Ant mailing lists so that we can address
>them before we get to a final release.
>
>Have fun
>
>         Stefan Bodewig


Question/Issue with jlink in Ant 1.2 Release Candidate

Posted by Ken Wood <kw...@i2.com>.
I tried jlink for the first time. I'm getting this error:

BUILD FAILED

jlink.xml:77: java.util.zip.ZipException: invalid entry crc-32 (expected 
0x4e3 but got 0x24b7559e)
java.util.zip.ZipException: invalid entry crc-32 (expected 0x4e3 but got 
0x24b7559e)
         at java.lang.Throwable.fillInStackTrace(Native Method)
         at java.lang.Throwable.fillInStackTrace(Compiled Code)
         at java.lang.Throwable.<init>(Compiled Code)
         at java.lang.Exception.<init>(Exception.java:42)
         at java.io.IOException.<init>(IOException.java:47)
         at java.util.zip.ZipException.<init>(ZipException.java:46)
         at java.util.zip.ZipOutputStream.closeEntry(Compiled Code)
         at 
org.apache.tools.ant.taskdefs.optional.jlink.jlink.mergeZipJarContents(Compiled 
Code)
         at 
org.apache.tools.ant.taskdefs.optional.jlink.jlink.link(Compiled Code)
         at 
org.apache.tools.ant.taskdefs.optional.jlink.JlinkTask.execute(JlinkTask.java)
         at org.apache.tools.ant.Target.execute(Compiled Code)
         at org.apache.tools.ant.Project.runTarget(Project.java)
         at org.apache.tools.ant.Project.executeTarget(Compiled Code)
         at org.apache.tools.ant.Project.executeTargets(Compiled Code)
         at org.apache.tools.ant.Main.runBuild(Compiled Code)
         at org.apache.tools.ant.Main.main(Main.java)

Which, by trial and error, I determined to be caused by
the "vbjorb.jar" entry. However, this jar file can be
used by java classes, it can be listed and extracted with
the 'jar' command, and can be expanded by ant with the
"unjar", since I used to do this job by unjarring all the jars
and then making a merged jar file from the extracted files.

Any ideas? (jdk1.2.2 on solaris 2.6, Ant 1.2rc)
For reference:
   <delete file="ALL.jar" />

   <jlink compress="false" outfile="ALL.jar">
     <mergefiles>
       <pathelement path="lib/vbjorb.jar"/>
       <pathelement path="lib/activation.jar"/>
       <pathelement path="lib/collections11.jar"/>
       <pathelement path="lib/entrust.jar"/>
        <pathelement path="lib/xml4j.jar"/>
       <pathelement path="lib/xt.jar"/>
     </mergefiles>
   </jlink>


At 05:40 PM 10/13/00 +0200, you wrote:

>optional.jar is not complete, some optional tasks are missing and
>might be added later.
>
>Please give this version a try, enjoy the new features and report bugs
>and problems to one of the Ant mailing lists so that we can address
>them before we get to a final release.