Paul Landes wrote: > I found two bugs when using `jde-import-all': [...] > This all highlights the need for some kind of automated testing. > Also, these bugs took many hours to track down and fix so please do > some basic testing after making big changes like adding 1.5 parsing > cedet code and inner class importing.
I did actually test this patch quite a bit before committing it, which is how I found the problem with the wisent 1.5 grammar -- see my message on 3 Jan, maybe you missed reading it, it might have saved you those hours of debugging. Without the wisent 1.5 grammar the patch worked fine. I noticed that it did result in a change in behaviour in that there was an extra \n between imports and the code, but other than that nothing that I would consider a bug. The main problem seems to be with the wisent 1.5 grammar, and I didn't back out that change immediately after my email about it because I was hoping that someone more familiar with how jdee and semantic interact would investigate and find the solution (in other respects the new grammar is much better when dealing with modern Java code). I do agree that a unit test suite would be a great idea though! Cheers, Len. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ jdee-devel mailing list jdee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jdee-devel
