This is due to a coding oversite that I just noticed yesterday. The reason is that for some reason task/type names are case-sensitive and names figured out by introspection are not.
These are normally handled by two different areas of code but for the add(typedef) introspection, the name is handled by both areas of code hence the oversite. I am commiting a fix for this now. Peter On Wednesday 15 October 2003 15:49, Dominique Devienne wrote: > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > > > peterreilly 2003/10/14 02:50:30 > > > > Modified: docs/manual/CoreTypes custom-programming.html > > Log: > > add note that only all lowercase typedefed classes work > > for custom components with add(type). > > > > <p> > > After the class has been written, it is added to the ant system > > by using <code><typedef></code>. > > + One thing to be aware of is that currently this will only work > > + if the definition name is all lower case. > > </p> > > Why is that Peter? I don't know/understand the rational beyond this. > > For regular typedefs, I can use any mix of lower/upper case, and even > dashes, and Ant works just fine. Why would add(Type) be any different? > > --DD > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
