| Age | Commit message (Collapse) | Author |
|---|
|
support explicitly listing the fields to use, via the new 'of' parameter.
We've also added any fields that start with $ to the default excludes list. Lombok itself can generate these fields ($lock of @Synchronized, for example), and in general they probably should count as effectively not part of the class.
|
|
mentioned. This functionality is used in quite a few places, so generalized it.
|
|
used to copy over to the method parameter of generated setters and constructors, but NotNull is not valid there. We've fixed it by limiting ourselves to annotations named 'NonNull', popular versions of which are legal in all the places we copy them to.
This leaves IDEA's NotNull out in the cold, but, lombok doesn't support IDEA anyway.
This is a workaround - once lombok supports type introspection we'll fix this properly.
|
|
|
|
|
|
|
|
when using @SneakyThrows (syntax colouring goes away, first character in the file is italic).
|
|
annotation @NotNull/@NonNull/@Nullable that is copied over by @Getter should no longer be causing the David Lynch bug.
|
|
generating. This really does seem to fix the David Lynch bug (#41).
|
|
the generated annotations seems to fix the David Lynch bug (issue #41).
Saving this now before further fiddling breaks things again.
|
|
ond depending on your eclipse version, a long stack trace.
The problem boiled down to the JSP compiler used by the help system also being instrumented with lombok, but that's not exactly the environment lombok was expecting. Fixed by simply disabling lombok when the environments don't match what we expect. In the process, the instrumentation has been made a little more robust; multiple separate OSGi modules can all be instrumented now, instead of the first one winning.
|
|
|
|
(reinierz).
|
|
|
|
|
|
|
|
@NonNull/@Nullable and getter/setter/constructor generation) to 0, as eclipse mysteriously fails for annotations copied WITH source positions, but only on methods (which happens for @Getter).
|
|
Conflicts:
src/lombok/eclipse/handlers/HandleData.java
src/lombok/eclipse/handlers/HandleEqualsAndHashCode.java
src/lombok/eclipse/handlers/HandleSetter.java
src/lombok/javac/handlers/HandleData.java
src/lombok/javac/handlers/HandleEqualsAndHashCode.java
src/lombok/javac/handlers/HandleSetter.java
|
|
|
|
|
|
|
|
|
|
have been removed.
|
|
http://groups.google.com/group/project-lombok/browse_thread/thread/a8d59daaf7c1ae09
|
|
|
|
googlegroups.
|
|
exceptions anytime you used a lombok annotation in implicit-value-parameter form (e.g: @Cleanup("release") instead of @Cleanup or @Cleanup(value="release").
Fixes issue #14
|
|
legal reasons for using it, so, changed it: explicitly setting 'callSuper=false' removes the warning. You only get the warning
if callSuper is false because that's the default.
Fixes issue #13
|
|
|
|
annotation
The constructor will test for null-values
The constructor and static constructor will copy the NonNull annotations from the fields
|
|
|
|
the parameter
@Getter will copy them to the getter method
Added @NonNull to lombok to support null-checks in the setter
|
|
|
|
|
|
|
|
reflected in all javadoc pages, and on the website itself.
The website design has been updated to have a link to the changelog and to mention the current version.
Addresses issue #9.
|
|
files)
|
|
'plus' nodes (e.g. concatenating the infix ", " and a field name literal such as "width=" into ", width=".
Also removed the [] brackets from the supercall, as, if you're chaining to another lombok-generated toString, those are superfluous - lombok's toString includes parentheses already.
|
|
now 'point at' the right position, instead of at the entire annotation. (it already did so for errors).
Fixes issue #11
|
|
new annotation, @EqualsAndHashCode.
Addresses issue #8
|
|
|
|
|
|
has now moved from HandleData to the new HandleToString.
|
|
entry now no longer causes ArrayIndexOutOfBoundsException, the setWarning method on a single item in an array initializer on eclipse
now generates the warning on just that node (like with errors), and the API of AnnotationValues has been updated to support setting errors/warning on any node.
|
|
|
|
|
|
|
|
hitting 'find callers' on a @Data annotation should find callers of the (static) constructor.
Right now it'll find callers to the *static* constructor ONLY. Letting it find callers of the public constructor if there is no static constructor just doesn't work.
|
|
|
|
If boolean fields already start with a typical getter prefix (is, has, or get), lombok's @Getter will no longer generate its own prefix as well, so a field named 'hasFoo' will result in a getter named 'hasFoo()', not 'isHasFoo()'.
Also, if any likely getter name already exists for a boolean, a getter will not be generated. Thus, if your field is called 'hasFoo', and you already have a method named 'isFoo', then @Getter will not generate anything (and warn, unless the getter is being generated due to @Data).
This last mechanism works by taking the field name *AND* any other likely base names (defined by the field name being named as prefix+baseName, with prefix being is/has/get), and then prefixing all the likely fieldnames with is/has/get, and checking if any method with that name exists.
Of course, this means weird things are going to happen if you have 2 fields named 'isFoo' and 'hasFoo', but then, you'd be a real idiot if you did that.
|
