> AntClassLoader really sucks. In XDoclet's xjavadoc module we're > resolving types in java codes by doing a Class.forName in some stages > and it's interesting to see that in most cases we're wasting > 95% of time in AntClassLoader (in all those spaghetti messy checks). > I know you can't change AntClassLoader radically in Ant1.x but at > least spend some time optimizing it :-)
Fair enough - could you give me a suitable test case (build file, whatever) which takes a long time and where a lot of that time is spent in AntClassLoader? If so, I'll happily have a look at improving it. Jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
