Stefan Bodewig wrote:
On Thu, 27 May 2004, Peter Reilly <[EMAIL PROTECTED]> wrote:
1) implicit element for macrodef
move from head to 1.6 branch
2) DynamicElementNS
move from head to 1.6 branch
Those are done, correct?
Just a few minutes ago :-)
3) Allow nested elements discovered by refection on to be
in the ant default namespace uri as well as the task's/types
namespace uri (the current rules are difficult to follow and
make build scripts look like line noise :-( aka xml ns hell)
Could you please (re-)start a dedicated thread for this so we have all
the details can resolve this once and for all time (well, a months or
two would be fine 8-)
Ok,
I will get my thoughts together and compose an e-mail with references to
the previous discussions.
Other things - maybe after 1.6.2
1) the antlibresolve task
after 1.6.2
Ok.
2) concat support for binary files
Done, correct?
Yes.
3) fix some classloading issues:
a) set the parent classloader in createClassloader() - most
likely a good thing and
I agree, but we may want to reopen this as a discussion in a separate
thread for more visibility.
Correct.
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".
There has been a discussion on these issues,
http://marc.theaimsgroup.com/?l=ant-user&m=108187987209772&w=2
5) add delete on exit feature to the <delete> task - needed to
antlib devl on windows
What does this do?
I was experimenting with an internal antlib.
And needed to remove the jar file from .ant/lib directory
so that the build was not affected by the classes in
the antlib jar file.
<target name="remove-install">
<mkdir dir="${install.dir}"/>
<delete>
<fileset dir="${install.dir}" includes="antextra-*.jar"/>
</delete>
</target>
Doing this is not possible on windows as the jar file is "open".
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:
http://marc.theaimsgroup.com/?t=107663433900002&r=1&w=2
6) add a do not follow symbolic links option to <delete> task
When is this needed? Why is the symlink support in <fileset> not
sufficient?
I see that this is an old issue:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1550
I do not think that this is sufficient.
see:
http://marc.theaimsgroup.com/?l=ant-user&m=107877912817024&w=2
The example is :
<>"
<delete includeEmptyDirs="yes">
<fileset dir="workdir" followsymlinks="no" defaultexcludes="no"/>
</delete>
which doesn't follow symlinks but also doesn't delete the symlinks
themselves."
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.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
