Alexander Klimetschek wrote > On Thu, Apr 1, 2010 at 09:12, Bertrand Delacretaz > <[email protected]> wrote: >> In the above example, the >> PackageFooBarClassWizMethodGetSomethingProblemComputeException name >> makes it very clear that there was a problem in the getSomething >> method of the Wiz class in package foo.bar, and the problem is a >> ComputeException. Bit of a longish name, but we all have cool IDEs, >> right? > > +1, but I think this isn't enough information. We should include the > author and revision number as well, so that people can easily find out > which version of the code to look at and who to blame on the mailing > list. > > Anything else? Maybe other interesting metadata such as the editor/IDE > in which the code was written, a short twitter-like status, etc. So we > get something like this: > > PackageFooBarClassWizMethodGetSomethingProblemComputeExceptionRevision201041WrittenByBertrandInEclipse35NiceWheatherToday Ah yes, and mentioning twitter, what about tweeting the exception to the project tweet? So the developers immediately see when their code is throwing an exception and they maybe can fix/change their code even before the user is able to summit a report to the issue tracker.
> > I think the JCP discussion are going to be very interesting! > Definitly! And its worth the effort! Carsten > Regards, > Alex > -- Carsten Ziegeler [email protected]
