ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Ellsworth <sc...@alodar.com>
Subject Re: fork option for jar task?
Date Sat, 08 Dec 2001 20:07:26 GMT
At 7:47 AM +0100 12/7/01, Stefan Bodewig wrote:
>On Thu, 6 Dec 2001, Scott Ellsworth <scott@alodar.com> wrote:
>
>>  Over on the cruise control list, it has been noted that Sun's tools
>>  are rather bad about releasing resources.  As best as I can tell,
>>  jar stabbed me in the back this morning.
>
>We don't use command line jar for the <jar> task, but a home brewed
>reimplementation of ZipOutputStream.  What is the problem you are
>seeing?  If it can be tracked down to the jar tasks, it probably is an
>Ant bug.

I believe it is a problem in the jar tasks.  If I build my jar with 
the jar task under cruise control, the file is at least occasionally 
marked as still open.  If it is an NFS mounted drive, it is not 
replaced.  NFS does this if a file handle to the file is still open.

This would not show up if the same jar was not built twice by the 
same process, so most uses of ANT would not suffer this failure. 
(Cruise control does not exit the process after a build - instead, 
the same process does all of the builds.)

The target for this is dirt simple:

   <target name="dist-debug" depends="compile-debug" 
description="Build release jar">
     <jar
       jarfile="${dist}/${baseJarName}-${DSTAMP}-debug.jar"
       basedir="${build-debug}"
       compress="false"
     />
   </target>

Scott
-- 

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


Mime
View raw message