You are right. I was creating javadocs in private level but getters and setters are needed only when field access is lower than public so link tag can not be used in javadoc. Then there is no need for this feature. Thank you very much Friedrik :)
"Fredrik Lindgren" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > -1, see archives regarding auto generated javadoc. > > IMO methods starting with get or set only really need javadoc if they > are _not_ getters or setters for properties according to the java beans > spec. If they do follow java beans patterns, what good is the extra > javadoc text compared to what you get without it? Anyone would > understand the method anyway. > > /Fredrik Lindgren > > Gokcer Gokdal wrote: > > I saw a nice feature in Ecslipse. While it creates getters and setters, it > > also creates some javadoc related with them. Idea can do it, also in > > addition I offer puttink links to related field if field is public. Fo > > example; > > > > public class Dummy { > > public Type field1; > > protected Type field2; > > /** > > * Getter for {@link field1}. <=== Link! > > */ > > public Type getField1(){ > > return field1; > > } > > /** > > * Getter for field2 <=== No link! > > */ > > public Type getField2(){ > > return field2 > > } > > } > > Same for setters... > > > > > _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
