--- Dominique Devienne <[EMAIL PROTECTED]> wrote:
> > 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.
If we choose (1), maybe we should create a new
directory src/resources (Java, not Ant) for those
non-Java config files that are supposed to live in
ant.jar . This way we don't pollute the codebase in
such a confusing manner.
-Matt
>
> --DD
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Yahoo! Messenger
Show us what our next emoticon should look like. Join the fun.
http://www.advision.webevents.yahoo.com/emoticontest
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
