On Thu, 8 May 2003 12:30 am, Costin Manolache wrote: > > The URI however should be chosen by the antlib author ( maybe based on some > rules specific to ant ), and should serve as an ID of the library. > > My proposal is to use the (main) package name. There are other options - > but I don't think every end user using it's own name for an antlib is a > good one. >
+1 I believe the URI should be defined by the antlib builder, not the user. It should be opaque - no semantic structure, at least from Ant's processing. An antlib should just declare to what namespace URI it belongs and then that antlib's defs would be accessible through that namespace in the build file. This would allow multiple antlibs to belong to a single namespace, which might be useful for extension purposes. So, something like this <antlib uri="blah"> <taskdef> <typdef> </antlib> Antlibs could potentially declare themselves to belong to the default namespace. This would handle Ant's existing optional tasks. This facility might be restricted to antlibs found in a particular location. A classloader could probably be associated with the URI, picking up all antlibs declaring the URI. Just some thoughts Conor
