On Fri, 04 Jun 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig wrote:
>
>>On Thu, 27 May 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
>>> 4) search paths for the import task
>>
>>Could you please expand on that?
>>
> This is something that could be done post 1.6.2.
> The idea is that <import file="x.xml"/> would
> be a bit like #include from cpp where there is an INCLUDEPATH
> that specifies where to look for "x.xml".
OK, I'd rather defer that after 1.6.2.
>>> 5) add delete on exit feature to the <delete> task - needed to
>>> antlib devl on windows
>>
>>What does this do?
>>
> One would need to do something like:
> <delete onfail="deleteonexit">
> <fileset dir="${install.dir}" includes="antextra-*.jar"/>
> </delete>
>
> There has been some discussion in ant-dev on this subject:
OK, I see. Doesn't look to difficult to implement, but harder to
provide decent feedback to the user: "Could not delete file X, will
try to delete it again later"?
You can add it to the list as far as I'm concerned.
>>> 6) add a do not follow symbolic links option to <delete> task
>>
>>When is this needed?
>
> One could have a build directory:
> build
> y
> x -> something outside the build directory that should not be deleted
>
> One cannot use the delete task to delete the build directory
> completely.
I see. Looking into DirectoryScanner it seems not that easy to fix
since the scanner will either recurse into x or exclude x based on the
followSymlink setting so anything we'd want to do would not only
affect Delete but probably any other task using DirectoryScanner as
well.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
