CONFIDENTIALITY NOTICE: This message is confidential and for the use only of the intended recipient. We've also come across the problem Curtis mentions. In general, you might want to avoid the javadoc affecting the code. I do understand, however, what Rodrigo says. What would be useful if, as well as importing the class, IDEA additionally offered to expand the class to its full class name. In the popup, you could then choose which option you need. This might also be useful for import popups in the code itself, as well as the JavaDoc.
Calum But for the javadoc to be correct, SomeClass must be imported or written with fullpath. If IDEA asks to import because of this error, then its behaviour is correct. If you don't want to import you should write it with fullpath. []'s, Rodrigo. > -----Original Message----- > From: Curtis R Cooley [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] > Sent: sexta-feira, 15 de fevereiro de 2002 14:13 > To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Subject: [Eap-list] @see feature can cause bad code dependencies > > > We ran into a little problem when the @see imported a class > that caused a bad > dependency in our project. > > When you have a javadoc comment like: > > /** > /* @see SomeClass > /* > > Idea 6 wants to import SomeClass, but that is not always what > the developer > wants to do. Sometimes you may want to redirect someone in > your docs to a > related Class but not actually use the class in the file. > > Just food for thought. > _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
