Age | Commit message (Collapse) | Author | |
---|---|---|---|
2009-07-27 | on javac: Warnings associated with specific values in annotation parameters ↵ | Reinier Zwitserloot | |
now 'point at' the right position, instead of at the entire annotation. (it already did so for errors). Fixes issue #11 | |||
2009-07-05 | More documentation. | Reinier Zwitserloot | |
2009-06-27 | [BUGFIX] For some reason, JCLiteral objects contain '1' or '0' (integers) ↵ | Reinier Zwitserloot | |
for booleans, not actual booleans. You can tell the difference via the getKind() method. hence, boolean fields in annotations were throwing unexpected type errors (Integer instead of Boolean). Fixed this. | |||
2009-06-19 | Added initial support for the @Data annotation. Currently produces getters ↵ | Reinier Zwitserloot | |
and setters only, not yet a constructor, toString, hashCode, or equals. HandleGetter and HandleSetter have been updated to handle static (theoretic; you can't put annotations on static fields normally). You can now make AnnotationValue objects using just an annotationNode and a target type, as well as check if a given annotationNode is likely to represent a target annotation type. This is in Javac and Eclipse classes. HandleGetter and HandleSetter can now be asked to make a getter/setter, and will grab access level off of a Getter/Setter annotation, if present. |