Wednesday, February 18, 2015

Re: How do I make the GWT Compiler see other modules in Eclipse?

I agree that the project dependency out to be enough.

I see the compiler finding foo:

   Loading inherited module 'Foo'
      Module location: file://c:/somepath/Workspaces/MyEclipse%20Professional%yadda%20yadda/foo/src/main/foopath/Foo.gwt.xml

But it can't see the Java source for the code inside Foo.

I'm stumped.


On Tuesday, February 17, 2015 at 5:44:07 PM UTC-6, Jens wrote:
A simple eclipse project dependency to foo should be enough. 

As the error says "can not find source" it does mean that the GWT compiler has actually found your foo.gwt.xml that you have inherited otherwise the compiler would complain about a missing GWT module. At work we have a common project that also holds GWT modules and we just add that common project to other projects as project reference/dependency to the build path. Works without problems. We do not add an explicit classpath entry, only the project reference.

-- J.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment