No more redundant Javadoc
When writing classes, I generally start with defining the private fields with Javadoc comments, then will use Eclipse to generate the public getters and setters. I like to Javadoc each field, but that Javadoc then needs to be repeated two more times (get and set), so I end up with needing to maintain 3 copies of the documentation.
One idea that was proposed was to add a generalised "{@include}" type tag in javadoc that would copy blocks of documentation from other objects. That way the refactoring process could just place a reference to the field documentation when creating getters and setters which wouldn't have to be changed when the field documentation was.
Does this sound like a feature that would make sense for JavaDoc 7? Or is there a reasonable alternative today?
