Looking at the bug report, it appears it was a bug in The Apple JDK, in which case WON'T FIX is appropriate.
I agree with Dion, WON'T FIX is better than CANNOT REPRODUCE. And we should not close bugs that we know are still in existence and not superseded, nor should we close feeature requests unless we have decided not to pursue them. - Brett Quoting Dion Gillard <[EMAIL PROTECTED]>: > On Mon, 26 Jul 2004 17:40:42 +0200, Carlos Sanchez > <[EMAIL PROTECTED]> wrote: > > IMHO > > I "cannot reproduce" because I've never tried, so people who see it will > > point out the steps to reproduce the issue (if it yet exists). > > "wont fix" means that I know the problem exists and that's not the case. > > > > but I have no problem to change it to whatever you prefer. > > Have a look at the bug report. I successfully reproduced it, and found > a workaround. The steps to reproduce it are in the bug report. > > Just because you haven't reproduced it doesn't mean someone else didn't. > -- > http://www.multitask.com.au/people/dion/ > > --------------------------------------------------------------------- > 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]
