This could be an OS issue. Referencing the mount could make the OS attempt
to mount the NFS directory, and if NFS hangs, the <available> task will sit
there and wait.
Remember too that it could take some time for the OS to determine it cannot
mount a particular filesystem, so that it could be the <available> task is
working, but you're not giving it long enough to verify that the directory
cannot be mounted. Give it about five minutes and see if it returns from the
<available> task.
You can also wrap your <available> task inside a <waitfor> task.
*<waitfor maxwait="30"
maxwaitunit="second"
timeoutproperty="never.mounted">
<available file="${nfs.mount}"/>
</waitfor>*
On Wed, Jul 22, 2009 at 1:19 PM, Cole, Derek E <[email protected]>wrote:
> I am having a problem with some build scripts I have written that have
> <available> tasks to set a property based on whether a particular mount
> is available on the build box. It seems like if the mount is not
> available for whatever reason, the build hangs at this point. Has anyone
> seen this behavior before?
>
>
--
David Weintraub
[email protected]
