very often javadoc is not a concern for me and I prefer not to mix code changes with javadoc fixes for source control purposes. In this case those javadoc errors are in my way.
-- fedor. > -----Original Message----- > From: Jason Boehle [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 5:54 AM > To: '[EMAIL PROTECTED]' > Subject: RE: [Eap-features] req: don't use red in the right bar for > errors in javadoc > > > Then fix your JavaDoc. What use is it if it's wrong? > > Jason Boehle > [EMAIL PROTECTED] > > > -----Original Message----- > From: Alain Ravet [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 20, 2002 4:57 AM > To: [EMAIL PROTECTED] > Subject: [Eap-features] req: don't use red in the right bar > for errors in > javadoc > > > Request : don't use red for errors in javadoc > Red should be kept for compilation errors. > > Ctrl-B drove me into some framework class, where the parameters were > renamed, but not the javadoc. It compiles fine, but the > right bar is almost > solid red. > > Alain Ravet > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
