Forgive me if my comments are stupid, I don't know the Ant Core that well...
I don't understand why you need to load custom tasks/types before the Core tasks/types. The current mechanism for loading them seems OK to me (awaiting <antlib> for a better mechanism though). Also, you assume the custom tasks/types are defined in properties files, which preclude using resources inside JARs (I have a resource: custom URL protocol similar to JBoss' one which I believe Ant should have) as you currently can (which I use). I personally believe we need a mechanism to load and configure other types of Ant extension points (Mappers, Conditions, Selectors, Filters, XmlCatalog resolvers, and even custom extension points) similarly to what's currently possible for tasks/types, which is good enough for now. By that I mean ways to configure the custom class using complex Ant objects represented as nested XML elements, share classloader, and have access to the Project reference. I misunderstood what you are trying to do, didn't I??? --DD -----Original Message----- From: Magesh Umasankar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 26, 2002 1:36 PM To: Ant Developers List Subject: [PATCH] User defined types and tasks to be loaded before default ones are... Hi, I am in need of a mechanism to be able to define user defined Tag->Class mappings *before* the names of the default types and tasks are mapped. I have attached a patch herewith. Comments? Cheers, Magesh -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
