Erik, Good news! I just wasn't sure if ant would try to instantiate the get task while trying to call the addXXX. I am obviously pretty green re: ant internals.
Thanks again, John-Mason Shackelford Software Developer NCS Pearson - Measurement Services 2510 North Dodge St. Iowa City, IA 52245 319-354-9200x6214 [EMAIL PROTECTED] > -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 15, 2002 3:38 PM > To: Ant Users List > Subject: Re: custom data type name collision > > > I don't think there is any reason to worry about a collision in your > case. The mapping for a nested element to a custom task is > done through > your Java codes naming conventions for your addXXX or createXXX or > addConfiguredXXX methods - not through a property file. > > I hope I'm understanding what you're talking about and answering the > right question, but if not let me know. > > Erik > > > Shackelford, John-Mason wrote: > > In writing a custom task that has a custom data type are > name collisions to > > be avoided at all costs? > > > > More specifically, I am writing a new set of tasks for > PVCS. To make it more > > flexible I have a top level tag called PCLI (the command > line controller for > > Version Manager) and then a data type AbstractCommand which > I extend for > > individual commands. One of the most commonly used PCLI > command is "Get." > > Can I get away with using "Get" for my subclass even though > it's the name of > > a core task or do I need to be content with PLCIGet or > something equally > > nasty? > > > > I realize after writing the above that the class names are > of secondary > > importance as the mapping from class name to tag is done > with ant directive > > or property file. Are task names and data types case sensitive? > > > > > > > > John-Mason Shackelford > > > > Software Developer > > NCS Pearson - Measurement Services > > 2510 North Dodge St. > > Iowa City, IA 52245 > > 319-354-9200x6214 > > [EMAIL PROTECTED] > > > > > ************************************************************** > ************** > > This email may contain confidential material. > > If you were not an intended recipient, > > Please notify the sender and delete all copies. > > We may monitor email to and from our network. > > > ************************************************************** > ************** > > > > -- > > 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]> **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. **************************************************************************** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
