How about adding a 'prefix' attribute to <taskdef> so you can say something
like:
<taskdef prefix="tomcat"
resource="/org/apache/tomcat/taskdefs.properties"
classpath="${jars}/tomcattask.jar" />
All the name get prefixed on the fly with the provided attribute. Kind of
like a poor man namespace mechanism ;-)
--DD
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED]
Sent: Monday, May 20, 2002 1:58 PM
To: Ant Developers List
Subject: Re: the tomcat 4.1 ant tasks
----- Original Message -----
From: "Erik Hatcher" <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Monday, May 20, 2002 11:22 AM
Subject: Re: the tomcat 4.1 ant tasks
> It sure would be nice if the Tomcat folks built a properties file that is
> included in the distribution so only one <taskdef> is needed rather than
all
> of those shown there. Anyone from there listening?! :)
>
> Erik
>
They are certainly listening, as remy wontfixed my 'please rename' bugrep
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9242) with
"I am not in favor of fixing this, as it's not a clean solution. Rather, I
think
Ant should add namespace support, as is currently being discussed on the
ant-dev
mailing list."
IMO the fact that we should do a long term solution does not obviate the
need to use sensible names for your tasks, and the tomcat 4.1 set have just
laid claim to some core verbs <deploy>, <list>. They are lucky we chose the
more verbose <serverdeploy> for our own deployment tasks.
Well, I suppose if we break anything, we know where to direct the bug
reports.
-steve
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
