ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <ddevie...@gmail.com>
Subject Re: Antlib autoloading (was Re: cvs commit: ant/src/testcases/org/apache/tools/ant/taskdefs AntlibTest.java)
Date Fri, 09 Sep 2005 21:57:07 GMT
On 9/9/05, Stefan Bodewig <bodewig@apache.org> wrote:
> > So, any ideas how this could be acomplished?
> Load all resources from META-INF/antlib.xml at startup and process
> them, I'd say.

But doesn't that go against Ant's tradition to not have auto-magic
things, but instead spell things out explicitly, usually in the build
file?

I'd rather we extend <typedef> to accept a <fileset> of AntLib jars to
load, possibly thru META-INF/antlib.xml, than auto-magically loading
all possible antlibs visible from the classpath. At least you can see
it and start looking at the jars it loads.

How would you know looking at a build file where a task is coming from
otherwise?

Also, for example, I have quite a few AntLibs which are in ant/lib,
and thus on Ant's classpath, but I don't use all of them in all my
builds. They're there because it's our official supercharged
production Ant distro, but loading all of them in builds that require
none or just a few is wasteful.

I personnally want to stay in control of what gets loaded in each
build. I don't want to prevent others to do it if they fancy it, as
long as it's not forced on me. --DD

PS: And BTW, Matt's point about conflict resolution is a good one.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message