| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
to @SneakyThrows, except with a keyword.
|
|
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
|
|
|
|
|
|
|
|
port the changes over to slideshow.html which has the same header. Fixed now, and uploaded to website.
|
|
|
|
|
|
ourselves.
|
|
|
|
|
|
|
|
@EqualsAndHashCode, and @Getter / @Setter documentation.
|
|
behaviour of javadoc tool
Worked on feature documentation
Renamed all "link to issue" to "Issue #n"
|
|
built .tar.bz2 file. Now it does. (use ant website-novideo to skip adding the videos, which reduces the upload from 18M to 1.4M).
|
|
isn't via git, but via an ssh upload.
|
|
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.
|
|
'download it instead' message, there's now still a link in the footer if you can't see the video to help folks with
a bad mix of plugins along.
|
|
files)
|
|
and modified the docs for @Data to refer to the docs of these new annotations.
The build script for the website has been updated to clean out the website build dir first, so files that used to exist but have now been tossed are no longer there.
There's also a special website-no-videos target which builds a website deployable without the videos. This makes the upload a lot faster if the videos haven't changed.
|
|
'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.
|
|
For whatever reason, the path to the javaagent in eclipse.ini on linux needs to be absolute.
|
|
JVM now correctly detects being on a mac, and using mac-specific code for finding and installing eclipses.
|
|
|
|
Honestly, we haven't tested it! Also updated instructions on how to
build the 64-bit version of the JVM, and generalized some of the loading
aspects of the DLL, as we now need to potentially try 2 of them.
|
|
A) FSUTIL is internationalized, so on non-english installs, we can't figure out if a disk is fixed.
B) I trust this better than fsutil for user control access (a.k.a. popups from hell) on vista.
C) fsutil.exe is in C:\windows\system32 so pretty sure it would be there, but there's always a chance it's not in the PATH, or otherwise not accessible.
|
|
|
