Open GoogleCodeExporter opened 9 years ago
Not sure whether this issue is addressing my concern directly, but I just ran
into errors while working with:
1. Lombok 1.12.2
2. JDK 8 (b108)
3. STS 3.4.0.RELEASE
4. early Eclipse JDT support for Java 8 as installed from
http://dist.springsource.com/snapshot/TOOLS/java8/e43
Prior to the installation of (4), Lombok was working as expected. After
installation I get dozens of the following error (see attached for details).
Lombok annotation handler class lombok.eclipse.handlers.HandleData failed
At a glance, it looks like the JDT API has some breaking changes in these
patches that support JDK 8, and this is causing Lombok to blow up with
NoSuchMethodErrors.
Do let me know if I should create a separate issue to address this problem.
Thanks!
Original comment by cbe...@gmail.com
on 8 Nov 2013 at 12:03
Attachments:
No, for now I think this is fine.
Original comment by r.spilker
on 8 Nov 2013 at 1:08
Added Eclipse BUG:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=424718
Works with this change.
Original comment by andrePan...@gmail.com
on 28 Dec 2013 at 7:27
bug in eclipse is now fixed, should be OK in release
Original comment by andrePan...@gmail.com
on 24 Jan 2014 at 7:23
We found an issue with val and lambdas. Something like this is fairly silly:
val r = someBool ? () -> 5 : () -> 7;
but you can type it, and it would cause exceptions if lombok was loaded. That's
been fixed. This more common case:
val r = () -> System.out.println();
Even gets a special error message explaining that lambdas just don't work that
way.
We did some more toying with JDK8 features in Eclipse Kepler with the JDK8
patch plugin, and didn't run into any major issues. 'val' in lambdas works,
@Cleanup in lambdas works, etc. I'm not closing this issue yet, as I want to do
a little more testing, especially as we get closer to the official Luna release
and the official JDK8 release.
This update (Fixing issues with val and lambdas) is in edge, here:
http://projectlombok.org/download-edge.html
Original comment by r.spilker
on 27 Feb 2014 at 8:40
Original issue reported on code.google.com by
r.spilker
on 22 Oct 2013 at 4:13