Javadoc+Style warnings using @Getter

226 views
Skip to first unread message

fabian...@web.de

unread,
Sep 14, 2009, 2:01:20 PM9/14/09
to Project Lombok
Imagine the following class:

public class User {

/**
* The internal user id.
*/
@Getter
private int idUser;

}

Using eclipse's javadoc warnings (for missing comments) I get the
following:
"Javadoc: Missing comment for public declaration" (at the variable
line).
Obviously I could disable the warning in the options, but then I would
loose them for all methods.

Additionally I get a Style type warning:
Unqualified access to the field User.idUser
Again I could disable this warning, but thats not the right way.

Third, the generated javadoc does not mention the getter.

I suppose the second one could be fixed by simply changing the
generated code to qualify the field.
For the other two, I have no clue.

Reinier Zwitserloot

unread,
Sep 15, 2009, 3:23:06 AM9/15/09
to Project Lombok
Disabling all warnings on generated code is in the works. Though,
those are some fairly archaic warnings you've got turned on there.

http://code.google.com/p/projectlombok/issues/detail?id=47


The fact that generated javadoc doesn't include warnings has been on
our radar since before lombok's release.

http://code.google.com/p/projectlombok/issues/detail?id=44

But, that 'unqualified access' error should not be happening. That's a
bug - all of the generated code should be using full qualifiers.

http://code.google.com/p/projectlombok/issues/detail?id=48

It would help if you could narrow down which of the things @Data does
is causing this, by using @Getter/@Setter/@ToString/@EqualsAndHashCode
instead, adding one at a time until the warning appears, then comment
on that issue. Thanks!

On Sep 14, 8:01 pm, "fabiankuer...@web.de" <fabiankuer...@web.de>
wrote:
Reply all
Reply to author
Forward
0 new messages