ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Corbin, James" <>
Subject RE: Ant1.5.2 EAR Problems --- Need Quick Feedback
Date Fri, 07 Mar 2003 23:00:43 GMT



-----Original Message-----
From: Steve Loughran [] 
Sent: Friday, March 07, 2003 3:22 PM
To: Ant Users List
Subject: Re: Ant1.5.2 EAR Problems --- Need Quick Feedback

----- Original Message -----
From: "Demyanovich, Craig - Apogent" <>
To: "'Ant Users List'" <>
Sent: Friday, March 07, 2003 13:43
Subject: RE: Ant1.5.2 EAR Problems --- Need Quick Feedback

> James,
> > I unzipped the ear and the application.xml file was making it
> > into the META-INF directory of the ear.  When I viewed the
> > jar using Winzip it wasn't visible which leads me to believe
> > that 1.5.2 is not producing a valid ear file.
> Good point about not producing a valid EAR file as opposed to not
> the application.xml file.  I hadn't thought of the situation in that way.
> > I moved back to 1.5.1 and everything worked including the
> > <metainf> tag that included my common utility jar.
> Reverting to 1.5.1 is my current solution, too.
> > I recommend staying away from 1.5.2.

It turned out that during the fixing to to get zip/jar/war/ear update=true
working properly, a bug went in which stops winzip reading the files.
Everything else does, like jar and the linux zip tools, but winzip is

The fix is in CVS, expect an update to 1.5.2 shortly, as in a few days or
more. And remember, it is only winzip that is having problems, nothing else.

To unsubscribe, e-mail:
For additional commands, e-mail:
This electronic message transmission contains information from the Company that may be proprietary,
confidential and/or privileged.
The information is intended only for the use of the individual(s) or entity named above. 
If you are not the intended recipient, be
aware that any disclosure, copying or distribution or use of the contents of this information
is prohibited.  If you have received
this electronic transmission in error, please notify the sender immediately by replying to
the address listed in the "From:" field.

View raw message