Lombok + GWT

[Richard Kolb]

Hello

I use Lombok a lot in pure Java. But in GWT, it breaks.

Is there a Lombok GWT expert that can help expand on this :
http://projectlombok.org/setup/gwt.html

1) What does this agent do in GWT specifically ?

2) I have not tried this agent with GWT, but Lombok does not work for me in dev mode.

On a simple Java bean decorated with @Data I get the following when GWT compiling (Java compile is fine, I use Lombok a lot ):
      [ERROR] Line 188: The method getId() is undefined for the type MyClass
      [ERROR] Line 190: The method getId() is undefined for the type MyClass

This happens for NoArgsConstructor AllArgsConstructor as well.

thanks

Richard

[Lenny Primak]

Lombok maintainers don't use GWT and its always on their back burner. I wouldn't expect to ever see good support for GWT in Lombok. It's sad but its true. I opened a couple of GWT issues and there have been plenty of other discussions about this, but such is life. 

--
You received this message because you are subscribed to the Google Groups "Project Lombok" group.
To unsubscribe from this group and stop receiving emails from it, send an email to project-lombo...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[rjdkolb]

Hi Lenny

Thanks. Marius and I would really like to use it with GWT.
Perhaps the 3 of us can scratch around to figure out how to make it work.

I think someone need to take down the page that says Lombok supports GWT.
I don't think it does at all.

regards
Richard

[Lenny Primak]

Making hacks to make it compile isn't the same as good support. 

Many features still don't work correctly, especially GWT designer. 

On Apr 4, 2013, at 11:30 AM, Tony Rah <xseg...@gmail.com> wrote:

Lombok works just fine in GWT - I use it everyday. There are a couple of caveats that aren't explicitly documented in that page. Here are the steps...

1. Add lombok to eclipse.ini so things work in eclipse workspace:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

-Xbootclasspath/a:{some.lombok.dir}/lombok.jar

2. Add lombok to your GWT build script so your automated compiles work:

<jvmarg value="-javaagent:${some.lombok.dir}/lombok.jar=ECJ" />

3. Add lombok to your eclipse launch config (in the VM args section) so your GWT debugging works:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

3.1: There is a defect in the Google plugin when using App Engine that will overwrite all other javaagents in the VM args section with the app engine javaagents. To work around this evil bug I made the .launch read-only on the file system. If you aren't using app engine then you need not be concerned about this.

Basically, lombok needs to exist everywhere there is compiling going on. Make sure that {some.lombok.dir} all points to the same version of lombok.

Good luck.

--

[Mat Jaggard]

Looks to me like someone needs to add the extra 2 locations to the documentation and figure out the 3rd location if it exists or put the caveat that designer is not supported into the documentation. Other than that, support for GWT sounds like its good.

We can't be held responsible for Google misbehaving with App Engine - but perhaps Tony could raise a bug for them? I've found the App Engine team pretty responsive in the past. Let us know the issue location so we can star it.

[Lenny Primak]

GWT Designer is very easy to use visual tool to design GWT apps 

https://developers.google.com/web-toolkit/tools/gwtdesigner/

It's IMHO a requirement really to be useful for GWT development. 

There were so many problems with Lombok and GWT that I am not even able to list them

If you try to use any advanced Lombok features in GWT code, it doesn't work,

Even outside eclipse, so your ECJ things won't help. 

On Apr 4, 2013, at 11:03 AM, Tony Rah <xseg...@gmail.com> wrote:

I wouldn't exactly call any of that a hack but to each their own. As far as GWT Designer goes I have no idea what does or doesn't work because I don't use it. Aside from the Designer what exactly isn't working for you? It doesn't really matter to me since it is working fine for all my projects but someone else might benefit from the information. 

[Richard Kolb]

Hi Tony

Thanks for the info, will give it a spin.

We use mainly Maven so maybe I can add some maven instructions for the gwt-maven-plugin.

regards

Richard

On 4 April 2013 17:30, Tony Rah <xseg...@gmail.com> wrote:

Lombok works just fine in GWT - I use it everyday. There are a couple of caveats that aren't explicitly documented in that page. Here are the steps...

1. Add lombok to eclipse.ini so things work in eclipse workspace:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

-Xbootclasspath/a:{some.lombok.dir}/lombok.jar

2. Add lombok to your GWT build script so your automated compiles work:

<jvmarg value="-javaagent:${some.lombok.dir}/lombok.jar=ECJ" />

3. Add lombok to your eclipse launch config (in the VM args section) so your GWT debugging works:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

3.1: There is a defect in the Google plugin when using App Engine that will overwrite all other javaagents in the VM args section with the app engine javaagents. To work around this evil bug I made the .launch read-only on the file system. If you aren't using app engine then you need not be concerned about this.

Basically, lombok needs to exist everywhere there is compiling going on. Make sure that {some.lombok.dir} all points to the same version of lombok.

Good luck.

On Wednesday, April 3, 2013 6:52:01 AM UTC-6, rjdkolb wrote:

--
You received this message because you are subscribed to a topic in the Google Groups "Project Lombok" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/project-lombok/WwiymShYBsg/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to project-lombo...@googlegroups.com.

[Lenny Primak]

This is the point.  This has nothing to do with Eclipse (ECJ) environment.

I don't think Tony is poking at the right place / environment here.

Also, GWT has the new 'enhanced developer mode' now that is totally different.

You received this message because you are subscribed to the Google Groups "Project Lombok" group.

To unsubscribe from this group and stop receiving emails from it, send an email to project-lombo...@googlegroups.com.

[Richard Kolb]

Hi Lenny.

Thanks, yes I don't use Eclipse for my GWT apps.

Everything is pure Maven.

I know Marius uses Eclipse with Maven and he hit the same issues,

Lets see if these flags will help

The developer mode is very important to me.

If the developer mode does not work, I can't use Lombok.

regards

Richard

[Lenny Primak]

Tony's comments are for ECJ ( = Eclipse Compiler Java )

and as far as I know do not  (or should not) make any difference for this particular issue.

Also, there is the 'new developer mode' introduced in GWT 2.5,

Not sure how this affects things as well.

Perhaps the maintainers can take a look at supporting GWT?

Just asking here ...

[Richard Kolb]

On 5 April 2013 08:42, Lenny Primak <lpr...@hope.nyc.ny.us> wrote:

Tony's comments are for ECJ ( = Eclipse Compiler Java )

and as far as I know do not  (or should not) make any difference for this particular issue.

Ah, thanks.

 

Also, there is the 'new developer mode' introduced in GWT 2.5,

Not sure how this affects things as well.

Yes, I can't code GWT without it :)

 

Perhaps the maintainers can take a look at supporting GWT?

Just asking here ...

I think the best way is to create test cases that work and some that do not.

Then maybe we can get the ones that don't work fixed.

I'm willing to make a couple of Maven test cases

regards

Richard

[Lenny Primak]

BIgger problem, at least for me, is that GWT designer doesn't even work at all

if lombok is installed in eclipse, forcing us to use 2 versions of eclipse,

one with lombok for everything, and one for GWT work, without lombok.

What a pain!!!

There are 10 issues already for GWT/Lombok that have been opened, even accepted,

for years now, with no progress, unfortunately.  Maybe adding more is a good thing, I don't know...

[Richard Kolb]

On 5 April 2013 08:50, Lenny Primak <lpr...@hope.nyc.ny.us> wrote:

BIgger problem, at least for me, is that GWT designer doesn't even work at all

if lombok is installed in eclipse, forcing us to use 2 versions of eclipse,

one with lombok for everything, and one for GWT work, without lombok.

What a pain!!!

Ouch, yes, that is unusable.

 

There are 10 issues already for GWT/Lombok that have been opened, even accepted,

for years now, with no progress, unfortunately.  Maybe adding more is a good thing, I don't know...

Can you please send me/us the links.

thanks

[Lenny Primak]

http://code.google.com/p/projectlombok/issues/detail?id=252

http://code.google.com/p/projectlombok/issues/detail?id=337

There are a few more, search like this:

http://code.google.com/p/projectlombok/issues/list?can=1&q=gwt&colspec=ID+Type+Status+Priority+Target+Component+Owner+Summary&cells=tiles

[Roel Spilker]

Hi all,

As one of the core Lombok developers I can tell you that we would love to have good GWT support.

The problem we gave is that since we are not GWT users ourselves we totally depend on others to tell us what works and what doesn't work. Also, it is not that we haven't enough to do already.

The main problem we have is that we ourselves don't feel the pain combined with the fact that we don't even know how to set up a representative test environment and keep (it) up-to-date.

That's why we do spend quite some time one helping others to find solutions and create patches that we review and incorporate.

So please, if you care about excellent GWT support in Lombok, tell us what you need so you can create tests, patches etc. Patches for documentation are welcome as well.

In the end, Lombok is an open source project for a reason and all work is done by volunteers. And the way it works best is if those are passionate about a certain feature. The current volunteers are not that passionate about GWT. If you are, please consider becoming a contributor.

Roel

[Richard Kolb]

Hi Roel.

Excellent, thank you.

regards

Richard

[Lenny Primak]

Very good.  Understanding this, can you (or other project maintainers)

close all the GWT-related issues to 'WontFix' and just say 

'Lombok is not supported with GWT at the current time & we are looking for volunteers.

This will reflect honestly what's going on.

I would love to volunteer to fix this (it is my pain point) but I would sadly admit

that I don't have the skill set to do this at this time.

[Richard Kolb]

Hi Lenny and Roel

I'd like to take over the issues that effect me.

So please don't close.

thanks
Richard.

[Roel Spilker]

Richard,

Don't worry, I'm not going to mark them all as WONTFIX.

I plan mark all this issues as GWT and possibly create a new status to park issues that we're not capable of fixing ourselves, so enthusiastic potential contributors from the community know what issues to take on.

Roel

[Richard Kolb]

Thanks Roel

[Reinier Zwitserloot]

In regards to issue 252 (https://code.google.com/p/projectlombok/issues/detail?id=252 )

I have looked at the current state of lombok's code and as far as I can tell this bug is at this point impossible. Can someone check? It should just not be happening at all.

In regards to issue 337: (https://code.google.com/p/projectlombok/issues/detail?id=337 )

No stacktraces of any kind mean this bug gets shunted to the bottom of the 'todo' list, and given that we're already swamped with lombok work, that is as good as 'never gonna look at it'. There are 2 basic ways we can handle a bug report like this:

* Do it right, install GWT, set up a basic project, re-familiarize ourselves with how it works (many many moons ago I did a project in GWT but I bet everything is very different new. Certainly that gwt designer thingamajig wasn't around back then), try to write some hello world examples, and see these bugs 'live', fixing them properly so that we can immediately test this work ourselves.

* Do it sloppely, follow the stacktrace, make a guesstimate as to what's going on, throw some basic debugging logging or a potential fix in there, build an edge release, and ask our GWT+Lombok users to see if our random shot in the dark did anything.

Now, if I were in your shoes, I would _much_ prefer option 1. But realistically speaking, option 1 means either a core contributor ends up doing something in GWT (chances: low), or, someone who does a lot of work in GWT picks up this role and starts handing us pull requests.

So, practically speaking then, you're looking at option 2. To facilitate option 2, post stack traces. No stack traces? No attention. I know, that's not exactly something we're proud of, but I'm guessing you'd rather get an honest answer than us leaving these bugs on 'acceptable' for another year.

Note that GWT's relatively frequent issues when interacting with other tools, and frequent changes, aren't helping. Whenever we see a bug report, especially a relatively vague one, our default action is: Let's just ignore it and hope it goes away. With specific stack traces, especially when those stack traces lead us to conclude that this bug is clearly our fault somehow, it becomes a lot harder for us to do that with a straight face.

TL;DR: Moar Stacktraces!

 --Reinier Zwitserloot

[Lenny Primak]

IMO, the only option here is option #1.  Option #2 won't work in this case,

there are just too many problems to accurately describe in issues / stack traces.

Since option #1's chances are low, and option #2 != good support, or any support IMO,

what really needs to happen is someone who actually cares to become a committer.

As you mentioned on the bottom, some of these issues may be tricky, may involve

requirements to use modified GWT libraries, etc. due to dependency incompatibility,

this isn't just pull requests, but a little more involved.

One hint, I think gwt-dev.jar needs to be re-packaged with jarjar to solve one of the dependency issues

So, will someone step up to the plate?

[Lenny Primak]

I just updated http://code.google.com/p/projectlombok/issues/detail?id=252

with the new stack trace.  The problem still persists.

[Axel]

Hi,

- In step 2, I do not know where is the build script, I am not using ant nor maven...

- In step 3.1, I do not know where is the file .launch you r talking about...Which directory should it be ?

- Does Lombok works with Super Dev Mode (GWT 2.5) ?

Thanks,

On Thursday, 4 April 2013 11:30:42 UTC-4, Tony Rah wrote:

Lombok works just fine in GWT - I use it everyday. There are a couple of caveats that aren't explicitly documented in that page. Here are the steps...

1. Add lombok to eclipse.ini so things work in eclipse workspace:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

-Xbootclasspath/a:{some.lombok.dir}/lombok.jar

2. Add lombok to your GWT build script so your automated compiles work:

<jvmarg value="-javaagent:${some.lombok.dir}/lombok.jar=ECJ" />

3. Add lombok to your eclipse launch config (in the VM args section) so your GWT debugging works:

-javaagent:{some.lombok.dir}/lombok.jar=ECJ

3.1: There is a defect in the Google plugin when using App Engine that will overwrite all other javaagents in the VM args section with the app engine javaagents. To work around this evil bug I made the .launch read-only on the file system. If you aren't using app engine then you need not be concerned about this.

Basically, lombok needs to exist everywhere there is compiling going on. Make sure that {some.lombok.dir} all points to the same version of lombok.

Good luck.

On Wednesday, April 3, 2013 6:52:01 AM UTC-6, rjdkolb wrote:

[Reinier Zwitserloot]

When you set up a GWT project, you get some XML files. These are ant files. At least, that's how it worked a while ago.

The launch config is the thing you get when you select 'Run...' or 'Debug...' from the eclipse run menu. There's a big textarea for entering JVM arguments. Put the stated line in there.

I don't know what super dev mode is.

 --Reinier Zwitserloot

--

[Richard Kolb]

Hi Reinier

A bit off topic here (hope you don't mind), but I have created a simple Maven project to at least show where the compile is failing with GWT 2.5.1 and Lombok 0.12.0
https://github.com/rjdkolb/testlombok-gwt

BTW,

Super dev mode allows the GWT to recompile bits of the JavaScipt from the Java without recompiling the entire project. It does this with a c++ GUI for speed reasons. So I am guessing that would be problematic.

I am not using Super dev mode, just a mvn package

I have decorated a class with @Data

When compiling I get
[INFO] --- gwt-maven-plugin:2.5.1:compile (default) @ testlombok ---
[INFO] auto discovered modules [org.openrap.testlombok.TestingLombok]
[INFO] Compiling module org.openrap.testlombok.TestingLombok
[INFO]    Validating units:
[INFO]       Ignored 82 units with compilation errors in first pass.
[INFO] Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.
[INFO]    Finding entry point classes
[INFO]       [ERROR] Errors in 'file:/tmp/testlombok/src/main/java/org/openrap/testlombok/client/TestingLombok.java'
[INFO]          [ERROR] Line 46: The method setAge(int) is undefined for the type LombokDomainClass
[INFO]          [ERROR] Line 47: The method getAge() is undefined for the type LombokDomainClass
[INFO]       [ERROR] Unable to find type 'org.openrap.testlombok.client.TestingLombok'
[INFO]          [ERROR] Hint: Previous compiler errors may have made this type unavailable
[INFO]          [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly

regards

Richard.

--
You received this message because you are subscribed to a topic in the Google Groups "Project Lombok" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/project-lombok/WwiymShYBsg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to project-lombo...@googlegroups.com.

[Reinier Zwitserloot]

rjdkolb, can you add a link to that github project to issue 252?

https://code.google.com/p/projectlombok/issues/detail?id=252

thanks.

[Richard Kolb]

Thanks Reinier,

Added it now.

[JonL]

rjdkolb,

Try modifying the executions similar to the below:

        <executions>
          <execution>
            <configuration>
              <extraJvmArgs>-javaagent:${lombok.jar.loc}=ECJ -Xmx512M -Xss1024k</extraJvmArgs>
            </configuration>
            <goals>

                           <goal>compile</goal>

                            <goal>test</goal>

                            <goal>i18n</goal>

                            <goal>generateAsync</goal>

           </goals>
          </execution>
        </executions>

[Richard Kolb]

Hi Jon,

Will try it tomorrow morning , thanks

regards

Richard

[Richard Kolb]

Hi Jon

This works perfectly, thanks

I've tested compile and dev mode in GWT.

I've updated the git project with the fix in the Maven plugin
https://github.com/rjdkolb/testlombok-gwt

It would be nice-er if I did not need to specify the location of the agent with a hard path in the properties.

Do you think there is a way around that ?

thanks

Richard

On 7 November 2013 01:08, JonL <jo...@percsolutions.com> wrote:

[Axel R]

Hi, does it work with SUPER DEV MODE (http://www.gwtproject.org/articles/superdevmode.html) ? (Because, Dev mode (the normal debug mode) will become obsolete I think, it is so slow to compile)

Thanls,

--
REGNOULT Axel

65 65 00 30

Sopocachi

LA PAZ - BOLIVIA

[Richard Kolb]

Hi Alex

Have not tried, but the source is on github so you can give it a bash.

regards

Richard

[Reinier Zwitserloot]

As long as you can add -javaagent:${lombok.jar.loc}=ECJ to whatever command ends up starting 'java' (the executable), it should work.

 --Reinier Zwitserloot

[Jaroslav Záruba]

Hello guys

Has anyone figured out the SuperDevMode? I can't seem to find a way to pass the javaagent argument to whatever is compiling the code in SDM. :(

I've tried to put it in the VM arguments on the Arguments tab in my SDM debug configuration, yet with no luck...

-Xmx512m -javaagent:C:\Users\jzaruba\.m2\repository\org\projectlombok\lombok\1.14.8\lombok-1.14.8.jar=ECJ

I get an ERROR for each reference to a lombok-getter (or setter) in my client code, and SDM won't start. :(

[Jaroslav Záruba]

Got it working now... Went back to launching the devserver via Maven from command line. I didn't realize I can (naturally) still configure how the local AppEngine gets started.

I'm actually happier with the way I launch the whole debugging monster now. :)

In case anyone would be interested:

<plugin>

<!--

We need to refer to a JAR location in gwt-maven-plugin

http://stackoverflow.com/a/14778330/224239 

http://maven.apache.org/plugins/maven-dependency-plugin/properties-mojo.html

-->

<artifactId>maven-dependency-plugin</artifactId>

<version>2.5.1</version>

<executions>

<execution>

<id>getClasspathFilenames</id>

<goals>

<goal>properties</goal>

</goals>

</execution>

</executions>

</plugin>

<plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>gwt-maven-plugin</artifactId>

<version>${gwt.version}</version>

<executions>

<execution>

<goals>

<goal>compile</goal>

</goals>

</execution>

</executions>

<configuration>

<compileSourcesArtifacts>

<!-- other projects containing GWT modules; these projects need to utilize maven-source-plugin -->

<artifact>net.jzaruba.xyz:Domain</artifact>

<artifact>net.jzaruba:GWT</artifact>

</compileSourcesArtifacts>

<!--

http://mojo.codehaus.org/gwt-maven-plugin/user-guide/appengine-launcher.html

https://groups.google.com/d/msg/maven-gae-plugin/Wrj-whTa3Yo/RDSKcWNQNaEJ

https://code.google.com/p/google-web-toolkit/source/browse/trunk/samples/mobilewebapp/pom.xml

-->

<server>com.google.appengine.tools.development.gwt.AppEngineLauncher</server>

<port>8080</port>

<appEngineHome>${appEngineSdk}</appEngineHome>

<appEngineVersion>${appengine.target.version}</appEngineVersion>

<runTarget>http://somedomain.com:8080/</runTarget> <!-- hosts file -->

<extraJvmArgs>-javaagent:${org.projectlombok:lombok:jar}=ECJ -agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n</extraJvmArgs>

</configuration>

</plugin>

Credits go also to thse guys: https://plus.google.com/102301209457369315970/posts/dY6x7YsFPW7

Cheers

  JZ

[foal]

Hi, 

I managed to run the latest Eclipse + GWT plugin + GWT 2.8.2 + Lombok 1.8.2 together

1. Add Lombok to eclipse (all standard steps)

2. Download special version of JDT used in GWT 2.8.2 (https://github.com/gwtproject/tools/raw/master/lib/eclipse/org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar)

3. To make compile action working add to the advanced section the following arguments

-javaagent:C:\Development\Lombok\gwt\lombok.jar=ECJ
-Xbootclasspath/p:C:\Development\Lombok\gwt\lombok.jar;C:\Development\Lombok\gwt\org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar

4. To make the CodeServer (GWT Dev mode) add the following JVM argument (Arguments section): 

-javaagent:C:\Development\Lombok\gwt\lombok.jar=ECJ

and add lombok.jar and org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar to Bootstrap Entries (Classpath section)

Maybe it will help somebody

Stas

[Reinier Zwitserloot]

I've added this to the gwt instructions on the site:

https://projectlombok.org/setup/gwt

I did go for a newer version of o.e.j.core. I assume that should be okay?

[foal]

Unfortunately, the latest version of o.e.j.core is not ok. The signatures of methods were changed since version used in GWT 2.8.2.

So for GWT 2.8.2 it must be org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar

But for the current development SNAPSHOT (2.8.3? 2.9?) you can and have to use the latest version of o.e.j.core jar (https://github.com/gwtproject/tools/raw/master/lib/eclipse/org.eclipse.jdt.core.source_3.13.102-CUSTOM-GWT-20180415.jar)

Stas.

[Reinier Zwitserloot]

Updated the docs again with this information.

[foal]

One more note. Method to update Bootstrap Entries in the CodeServer (GWT Dev mode) run configuration is working, but disable default updates, so if you will change maven dependencies it will not reflect in the CodeServer classpath. To fix it you have to select Restore Default Entries on the Classpath tab and then add 

-Xbootclasspath/p:C:\Development\Lombok\gwt\lombok.jar;C:\Development\Lombok\gwt\org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar

to the VM arguments of the run configuration (the same as for compile action)

Best, 

Stas

[Linus Kamb]

Hi all,

I was encouraged by this thread, as I do love lombok and was hoping to be able to use in my GWT project as well.

However, at this point, following the above instructions, I am still getting compile errors during GWT compile.

I have -javaagent:/Applications/Eclipse.app/Contents/Eclipse/lombok.jar=ECJ in my eclipse.ini file.

I have added 

-javaagent:/local/software/lombok/lombok_1.18.18.jar=ECJ

-Xbootclasspath/p:/local/software/lombok/lombok_1.18.18.jar:/local/software/lombok/org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar

to the VM arguments for GWT compile.

(The lombok jar in the eclipse dir is also 1.18.18.)

I am running eclipse 2018-09 (yes, I know..) with eclipse plugin and GWT 2.8.1 on a mac.

Any thoughts or suggestions?

thanks so much.

[Stanislav Spiridonov]

Hi,

Maybe an issue in GWT 2.8.1. The org.eclipse.jdt.core_3.11.2-CUSTOM-GWT-2.8-20160205.jar is for GWT 2.8.2.

The easiest way to check it -  use GWT 2.8.2 instead of 2.8.1. If it will work with GWT 2.8.2, so the problem is in org.eclipse.jdt.core version and you should find the correct one for GWT 2.8.1

Best,

Stas

--

You received this message because you are subscribed to a topic in the Google Groups "Project Lombok" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/project-lombok/WwiymShYBsg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to project-lombo...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/project-lombok/320ebf0a-bd7e-420f-9d55-19daf4f8928dn%40googlegroups.com.

[Linus Kamb]

Yeah, I tried to use gwt 2.8.2, but the eclipse GWT plugin comes with 2.8.1, and when I tried to add 2.8.2, everything broke.  I'm sure I did it wrong.  I'll try some more.

Thanks very much for your reply!