As good as it gets? I like the whopper sized error message, I think it is better than listing what classes are in/not in. Frankly, I think it is one of the best error messages I have ever seen. It actually gives you a selection of likely solutions then and there. You don't have to search the docs to divine the solutions. That is very user friendly, and I found it quite helpful when I ran into it. I doubt a list of what classes were and wern't there would be nearly as helpful, because the user would just think, "Ant has a bug, it's not loading all of it's classes correctly."
Listing what is in/not in could be helpful for developers, but not so much for users who won't know why the class isn't in (until they read the whopper sized error message). -Gus Erik Hatcher wrote: > > Well, yeah, but how often has that not been used by users and we field > questions that have the answer "put junit.jar in ANT_HOME/lib and call us in > the morning"? :) > > But I guess Steve's new whopper sized error message when its encountered is > as good as it gets. :/ > > ----- Original Message ----- > From: "Conor MacNeill" <[EMAIL PROTECTED]> > To: "Ant Developers List" <[EMAIL PROTECTED]> > Sent: Wednesday, June 26, 2002 8:19 PM > Subject: Re: cvs commit: jakarta-ant/src/main/org/apache/tools/ant Main.java > Diagnostics.java > > > Erik Hatcher wrote: > > > Another handy diagnostic would be to walk all the classes in both > > > defaults.properties files and attempt do Class.forName and see if they > are > > > there. > > > > ant -debug > > > > :-) > > > > Conor > > > > > > > > -- > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
