github/lombok.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2014-03-26	[i660] canEqual is now protected instead of public.	Roel Spilker
	Also fixed the total lack of canEqual in the usage examples.
2014-01-19	Issue 625: use (even) better primes for hashcodes	Roel Spilker

2014-01-09	[#625] Instead of '31' as a prime number for hashCode(), use something else. ↵	Reinier Zwitserloot
	31, probably owing to its inclusion in Effective Java, is overused, as proven by Maaartinus in issue 625. Switching to 277 instead. Also, 1231/1237 pair used for booleans has been replaced by 2591/2609.
2012-07-16	fixed tests since Robbert Jan's fix for issue 377.	Reinier Zwitserloot

2012-04-29	Issue 366: don't call the getter twice, fixed for Eclipse.	Roel Spilker

2011-11-01	Fixed unit tests to take into account work on issue 289 and 287.	Roel Spilker

2011-01-17	Some of the tests weren't succeeding (and haven't for a while now) since ↵	Reinier Zwitserloot
	fixing the bug where lombok will call equals(SomeSpecificType) instead of equals(Object) from data. This commit rectifies this by updating the tests.
2010-11-08	Added support for canEqual in ecj	Roel Spilker

2010-07-22	toString(), equals(), and hashCode() now use getX() instead of x if either ↵	Reinier Zwitserloot
	it exists OR it will be generated by some other lombok annotation, addressing issue #110. code deduplication by removing HandleData's scanning for fields, which is now no longer done; the sub-parts of Data (Getter, Setter, RequiredArgsConstructor, etc) take care of it now. fix for class-level @Getter/@Setter, which used to go for every field. Now they skip the usual fields (static, for setters final, and $ prefixed fields). Bugfix for @Data not recognizing that it should let field-level @Getter/@Setter take care of generating the getter/setter for multi field declarations (@Getter int x, y);
2010-07-22	Added more tests, one of which tests usage of .getX() in toString, equals, ↵	Reinier Zwitserloot
	and hashCode, which isn't fully working yet, so this test still fails.