ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominique Devienne" <DDevie...@lgc.com>
Subject RE: ResourceCollections
Date Fri, 01 Apr 2005 19:57:03 GMT
> > What's difficult already?
> > It's like a Java import basically.
> > You declare what you're using. What's wrong with
> > that? --DD
> 
> hmm... using the project attributes:
> 
> <project name="foo" default="bar"
>          xmlns:fs="antlib:org.apache.tools.ant.types.selectors"
>
xmlns:rs="antlib:org.apache.tools.ant.types.resources.selectors"
>          xmlns:ac="antlib:net.sf.antcontrib">
> 
> It's just the package names are quite long.  Could we
> auto-alias the uris so that the user setup might be
> like below?
> 
> <project name="foo" default="bar"
>          xmlns:fs="ant.fileselectors"
>          xmlns:rs="ant.resourceselectors">

I'd prefer at least

antlib:org.apache.ant.mappers
antlib:org.apache.ant.selectors
antlib:org.apache.ant.rescources.selectors

And we have the choice of (1) actually putting the antlib.xml
files in these directories, or (2) create yet another mechanism
to map an AntLib URI to its actual XML descriptor.

(we have one already with <typedef> I think, but I'd prefer
to stay with an automagic URI approach).

I could leave with (1).

For (2), we could use META-INF/services/antlibs.properties, which
would contain a mapping URI (w/o antlib: prefix for example) to
Descriptor Resource:

org.apache.ant.selectors org/apache/tools/ant/types/selectors/antlib.xml

(1) is simpler to put in place.
(2) is more flexible, but may be a little too much indirection.

--DD

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


Mime
View raw message