Google Web Toolkit: April 2017

Sunday, April 30, 2017

Re: GWTReact Release and Roadmap

Great work.

We are just starting down the path of React+GWT and glad to see the project moving forward

On Sun, Apr 30, 2017 at 10:27 PM, Paul Stockley <pstockley1@gmail.com> wrote:

I have just released a new version of the GWTReact projects to support GWT 2.8.1

As of this release, I will no longer be maintaining the MobX and Redux projects. Our company is not using them currently and I don't have the time to keep them updated. In the future, we may update MobX if we start using it in production. If you would like take over maintenance of either of these projects please let me know.

Road Map

With the current release, I feel pretty good about the quality of the projects. We are starting to use both gwt-interop-utils and gwt-react in our production code with excellent results. However, I think to get to a 1.0 release I need to make the following changes:

Migrate gwt-interop-utils to use the new GWT base project
Migrate gwt-react to use elemental 2
I will start working on these objectives in a month or two. The main determining factor on how quick this happens will be how fast elemental 2 matures.

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Cheers,

Peter Donald

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWTReact Release and Roadmap

For what it's worth, as a Redux maintainer I can assure you that Redux is very stable and not going to meaningfully change (at least at the API level) from here on out :)

On Sunday, April 30, 2017 at 8:27:10 AM UTC-4, Paul Stockley wrote:

I have just released a new version of the GWTReact projects to support GWT 2.8.1

As of this release, I will no longer be maintaining the MobX and Redux projects. Our company is not using them currently and I don't have the time to keep them updated. In the future, we may update MobX if we start using it in production. If you would like take over maintenance of either of these projects please let me know.

Road Map

With the current release, I feel pretty good about the quality of the projects. We are starting to use both gwt-interop-utils and gwt-react in our production code with excellent results. However, I think to get to a 1.0 release I need to make the following changes:

Migrate gwt-interop-utils to use the new GWT base project
Migrate gwt-react to use elemental 2
I will start working on these objectives in a month or two. The main determining factor on how quick this happens will be how fast elemental 2 matures.

GWTReact Release and Roadmap

I have just released a new version of the GWTReact projects to support GWT 2.8.1

As of this release, I will no longer be maintaining the MobX and Redux projects. Our company is not using them currently and I don't have the time to keep them updated. In the future, we may update MobX if we start using it in production. If you would like take over maintenance of either of these projects please let me know.

Road Map

With the current release, I feel pretty good about the quality of the projects. We are starting to use both gwt-interop-utils and gwt-react in our production code with excellent results. However, I think to get to a 1.0 release I need to make the following changes:

Migrate gwt-interop-utils to use the new GWT base project
Migrate gwt-react to use elemental 2

I will start working on these objectives in a month or two. The main determining factor on how quick this happens will be how fast elemental 2 matures.

Saturday, April 29, 2017

Re: gwt elemental newbie

Elemental 1 and 2 are a bit different, both exposes the "whole" HTML5 API, elemental 1 using jsni and elemental 2 using jsinterop. But elemental 1 has other tools that look like elemental 2 is not going to include like shared json implementation and hight-performance collections. And finally and most important, elemental 2 is pretty unstable right now so it probably will break your compilation on each alpha release as you have seen in the branflake code. Just update to make it work.

More info about elemental 1 here http://www.gwtproject.org/articles/elemental.html.

On Sat, Apr 29, 2017 at 3:51 PM <gwttechg@gmail.com> wrote:

Hello,

I am starting to learn gwt elemental.
I've started with the code here: https://gist.github.com/branflake2267/8e4b9d4f2dc594fe21a125155516ec97

but there are some compile time errors. See attached screenshot with comments on the lines with errors, and my crude attempts at workarounds.

The workarounds seem to fix the compile time errors, but when running the app there is a runtime exception at this line of code:

HTMLDocument document = new HTMLDocument(); //Error- Illegal constructor.

Thanks in advance for your help

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

gwt elemental newbie

Hello,

I am starting to learn gwt elemental.
I've started with the code here: https://gist.github.com/branflake2267/8e4b9d4f2dc594fe21a125155516ec97

but there are some compile time errors. See attached screenshot with comments on the lines with errors, and my crude attempts at workarounds.

The workarounds seem to fix the compile time errors, but when running the app there is a runtime exception at this line of code:

HTMLDocument document = new HTMLDocument(); //Error- Illegal constructor.

Thanks in advance for your help

Friday, April 28, 2017

Re: GWT 2.8.1 - Could not find artifact org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1

Hello,

For me using gwt-maven-plugin 2.8.0 and gwt-* 2.8.1 i had errors when compiling (ClassNotFound ... RegExp ...).

Applying Thomas suggestion fixed the issue.

On Thursday, April 27, 2017 at 2:38:47 PM UTC+3, Ignacio Baca Moreno-Torres wrote:

Actually, since this commit, https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/8b456fedae820cfdcdc581d18900f7244cf51234 using a gwt-dev and gwt-user explicit dependency in your module should disable auto-inclusion of gwt dependencies, so the plugin should work.

On Thu, Apr 27, 2017 at 10:24 AM Thomas Broyer <t.br...@gmail.com> wrote:

On Thursday, April 27, 2017 at 9:30:36 AM UTC+2, Ignacio Baca Moreno-Torres wrote:
Yep, should be released... but it is pretty weird that the plugin should be released on each GWT version, this and other important issues like better multi-module support was the motivation to start the new generation plugin by Thomas Broyer (https://github.com/tbroyer/gwt-maven-plugin). We'll release a new version just to match the GWT version number during this week. In the meantime, you may try to migrate to the new generation one, Thanks!

Also, this should work: https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Thursday, April 27, 2017

Re: GWT 2.8.1 release

I was running 2.8.0, everything was fine. now that I upgraded to 2.8.1, my gwt unit tests are failing: Anything I need to add?

java.lang.NoClassDefFoundError: com/google/gwt/dev/util/arg/ArgHandlerFilterJsInteropExports  	at com.google.gwt.junit.JUnitShell.getUnitTestShell(JUnitShell.java:684)  	at com.google.gwt.junit.JUnitShell.runTest(JUnitShell.java:672)  	at com.google.gwt.junit.client.GWTTestCase.runTest(GWTTestCase.java:421)  	at junit.framework.TestCase.runBare(TestCase.java:141)  	at junit.framework.TestResult$1.protect(TestResult.java:122)  	at junit.framework.TestResult.runProtected(TestResult.java:142)  	at junit.framework.TestResult.run(TestResult.java:125)  	at junit.framework.TestCase.run(TestCase.java:129)  	at com.google.gwt.junit.client.GWTTestCase.run(GWTTestCase.java:247)  	at junit.framework.TestSuite.runTest(TestSuite.java:252)  	at junit.framework.TestSuite.run(TestSuite.java:247)  	at junit.framework.TestSuite.runTest(TestSuite.java:252)  	at junit.framework.TestSuite.run(TestSuite.java:247)  	at org.codehaus.mojo.gwt.test.MavenTestRunner.doRun(MavenTestRunner.java:105)  	at junit.textui.TestRunner.start(TestRunner.java:183)  	at org.codehaus.mojo.gwt.test.MavenTestRunner.main(MavenTestRunner.java:63)  Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.util.arg.ArgHandlerFilterJsInteropExports  	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)  	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)  	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)  	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)  	... 16 more

On Tuesday, April 25, 2017 at 3:30:21 PM UTC-4, Colin Alworth wrote:

I'm very pleased to announce the release of GWT 2.8.1. This contains many bugfixes and a few enhancements to JsInterop.

Highlights from release notes:

Elemental1's JSON parser now correctly throws an exception when a string, object, or array is not correctly ended.

Support filtering JsInterop types for export, with whitelist/blacklist and wildcards. The -generateJsInteropExport flag is still used to enable the feature, but -includeJsInteropExport and -excludeJsInteropExport now exist to specify packages with optional * wildcards. Later arguments and patterns override earlier ones.

Support "*" (any) and "?" (unknown) types as a JsType native name. The "Unknown" type can be preferred over Object if the type is unknown, while "any" is preferred supertype of any JS type, including primitives.

Additionally, this supports the recent beta release of jsinterop.base and elemental2, available from Maven Central.

Please check out the full release notes, then download the release zip or update your project to get version 2.8.1 from Maven Central.

Chrome Extension Message Passing API no longer working in GWT 2.8...?

Hello all...

I'm a developer on a project that uses GWT. We had been using GWT 2.6 for a long time, and finally moved to GWT 2.8 w/Java 1.8.

Part of this project is a Chrome extension, where our web app needs to communicate with the extension. This was working fine until we upgraded out project.

Now, there may be other code-related things going on that is causing this, but I thought I'd check here to see if anyone knows of GWT 2.8 possibly breaking Chrome extension APIs, specifically the Chrome "Message Passing" API:

https://developer.chrome.com/extensions/messaging

The web app attempts to connect to the extension using chrome.runtime.connect(appId). This worked fine in the past, but has now stopped working (in prior versions of our code, the extension receives the connection attempt; in current code, the connect method returns a valid "port" object, but the extension never receives the connection).

Anyone know of any conflicts between GWT 2.8/JsInterop/etc. and Chrome's proprietary APIs?

- Tim

Trying to run Super Dev Mode in Server

Hi,

I've made a deploy of my GWT project (2.8) in Google App Engine. When loading host page in GAE i get this error:

"Couldn't load "my entrypoint" from Super Dev Mode server at.... "my GAE URL server:9876".

I'm using GWT Eclipse Plugin and Google Cloud Tools for Eclipse Plugin.

It seems I've uploaded Super Dev Mode compiliation but not GWT server compilation. What can be wrong?

This is the Hostpage:


<!doctype html>
<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <title>DataEntry</title>
    <script type="text/javascript" language="javascript" src="dataentry/dataentry.nocache.js"></script>
  </head>

  <body>
<!--     <iframe src="javascript:''" id="__gwt_historyFrame" tabIndex='-1' style="position:absolute;width:0;height:0;border:0"></iframe> -->
        <div id="gwtContainer"></div>
  </body>
</html>

Re: CAn I easily integrate Angular JS with GWT and will it work flawlessly and efficiently.

Yes, you can (for Angular 2):

https://github.com/ltearno/angular2-gwt

http://lteconsulting.fr/angular2boot/

You can make GWT work with any javascript framework (not just angular).

On Thursday, April 27, 2017 at 7:39:55 AM UTC-4, Sachin Chaudhari wrote:

CAn I easily integrate Angular JS with GWT and will it work flawlessly and efficiently. Please reply.

context in GWT compiled javascript

I have a very special requirement. My customer has a very old web application which only runs IE8. This customer doesn't allow me to change its source code except that I can add a <script> in original web page to include *.nocache.js file I must use GWT to make it run in all modern browsers. Some pages have <body onload='window.document.....; window.document.all.....more javascript code' /> and <div onclick='some javascript code' />. My GWT code must change javascript in inline onload javascript body. In development mode, I noticed original web page has one extra link that points to source code server(?), which is generated by Eclipse plugin. I also noticed onload is called before compilation. In SSO, I think my GWT compiled code should run before original web page onload. How do I make onload is called after my GWT compiled code finishes execution in development and production mode? What is context relation between window object in original js code and window object in my GWT compiled code in development and production mode?

Thanks!

David

Re: How to use custom elements (web components) with JsInterop and Elemental 2?

Solved!

Had to remind myself of having to assign my custom element to the window object, see https://github.com/gwtproject/gwt/issues/9500

.i.e in my HTML:

customElements.define("my-app", MyApp);

window.MyApp = MyApp; // This additional line is required

.. and in GWT I had to use name="MyApp", or rename class to MyApp

@JsType(isNative = true, name="MyApp", namespace = JsPackage.GLOBAL)

public class MyAppElement extends HTMLElement {

...

}

On Thursday, April 27, 2017 at 2:36:06 PM UTC+2, Anders Forsell wrote:

Hello again,

I have a custom element defined in HTML and trying to communicate with it from GWT and with JsInterop.

Similar to how I can create a div element and cast it to the Elemental 2 HTMLDivElement, I have defined MyAppElement extending Elemental 2 HTMLElement
and using the same JsInterop annotations as for HTMLDivElement:

@JsType(isNative = true, namespace = JsPackage.GLOBAL)
public class MyAppElement extends HTMLElement {
...
}

The following works fine:

Element element = DomGlobal.document.createElement("div");
HTMLDivElement divElement = (HTMLDivElement) element;

... but for my custom element I cannot cast it to MyAppElement:

Element element = DomGlobal.document.createElement("my-app");
MyAppElement myAppElement = (MyAppElement) element; // Throws ClassCastException

What am I missing?

How to use custom elements (web components) with JsInterop and Elemental 2?

Hello again,

I have a custom element defined in HTML and trying to communicate with it from GWT and with JsInterop.

Similar to how I can create a div element and cast it to the Elemental 2 HTMLDivElement, I have defined MyAppElement extending Elemental 2 HTMLElement

and using the same JsInterop annotations as for HTMLDivElement:

@JsType(isNative = true, namespace = JsPackage.GLOBAL)

public class MyAppElement extends HTMLElement {

...

}

The following works fine:

Element element = DomGlobal.document.createElement("div");

HTMLDivElement divElement = (HTMLDivElement) element;

... but for my custom element I cannot cast it to MyAppElement:

Element element = DomGlobal.document.createElement("my-app");

MyAppElement myAppElement = (MyAppElement) element; // Throws ClassCastException

What am I missing?

Re: Unable to add a new module to the webapp using Eclipse

I think first try same process with GWT 2.7. then see whats the effect.

On Thursday, April 27, 2017 at 12:12:36 AM UTC+5:30, HS wrote:

Hello,

I created a sample GWT webapp using the Eclipse plugin, and it runs perfectly.

But when I try adding a new module by,

    a) Right-clicking the above webapp project,
    b) Selecting the "New | Other... | GWT Classes | Module" option; and
    c) Clicking the Next button on the wizard

nothing happens - the wizard continues to remain on the same wizard-page!

I next copy-pasted the package/directory structure of my working webapp, and made suitable changes to the 'NewModule.gwt.xml' and its contents; also changed Java class names appropriately.

But when I run GWT Compile on the project (by right clicking the project in Eclipse), it only compiles the original webapp, completely ignoring my 'NewModule' module that I manually created on the file-system.

What am I doing wrong?
Is there a command-line method to ease the process of a new module-creation in an existing web app, or, ideally, creating it as a stand-alone entity?

I'm using GWT 2.8 with Eclipse Neon, on Ubuntu 16.04.

Regards,
/HS

CAn I easily integrate Angular JS with GWT and will it work flawlessly and efficiently.

CAn I easily integrate Angular JS with GWT and will it work flawlessly and efficiently. Please reply.

Re: GWT 2.8.1 - Could not find artifact org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1

Actually, since this commit, https://github.com/gwt-maven-plugin/gwt-maven-plugin/commit/8b456fedae820cfdcdc581d18900f7244cf51234 using a gwt-dev and gwt-user explicit dependency in your module should disable auto-inclusion of gwt dependencies, so the plugin should work.

On Thu, Apr 27, 2017 at 10:24 AM Thomas Broyer <t.broyer@gmail.com> wrote:

On Thursday, April 27, 2017 at 9:30:36 AM UTC+2, Ignacio Baca Moreno-Torres wrote:
Yep, should be released... but it is pretty weird that the plugin should be released on each GWT version, this and other important issues like better multi-module support was the motivation to start the new generation plugin by Thomas Broyer (https://github.com/tbroyer/gwt-maven-plugin). We'll release a new version just to match the GWT version number during this week. In the meantime, you may try to migrate to the new generation one, Thanks!

Also, this should work: https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: How to get the Document object with Elemental2

DomGlobal.document did the trick.

Thanks!

On Thursday, April 27, 2017 at 10:35:45 AM UTC+2, Jens wrote:

If I remember correctly the class is named DomGlobal.

-- J.

Re: How to get the Document object with Elemental2

If I remember correctly the class is named DomGlobal.

-- J.

Re: GWT 2.8.1 - Could not find artifact org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1

On Thursday, April 27, 2017 at 9:30:36 AM UTC+2, Ignacio Baca Moreno-Torres wrote:

Yep, should be released... but it is pretty weird that the plugin should be released on each GWT version, this and other important issues like better multi-module support was the motivation to start the new generation plugin by Thomas Broyer (https://github.com/tbroyer/gwt-maven-plugin). We'll release a new version just to match the GWT version number during this week. In the meantime, you may try to migrate to the new generation one, Thanks!

Also, this should work: https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html

How to get the Document object with Elemental2

Hi,

I'm currently migration from Elemental to Elemental2 beta and have code that uses the static Browser operations such as Browser.getDocument().

How would I get the Window or Document object with Elemental2 ?

Re: GWT 2.8.1 - Could not find artifact org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1

Yep, should be released... but it is pretty weird that the plugin should be released on each GWT version, this and other important issues like better multi-module support was the motivation to start the new generation plugin by Thomas Broyer (https://github.com/tbroyer/gwt-maven-plugin). We'll release a new version just to match the GWT version number during this week. In the meantime, you may try to migrate to the new generation one, Thanks!

On Thu, Apr 27, 2017 at 5:59 AM Freddy Boucher <freddy.boucher@gmail.com> wrote:

Hi,

Thanks for the hard work about GWT 2.8.1.

Do you plan to release org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1 ?

Thanks

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Wednesday, April 26, 2017

Re: Why incremental compiler option defaults to OFF?

I have no problems running the gradle tasks. The main problem is a lot of manual work in the process of debugging the code.

gwtDev ->debug code->gwtStop->gwtRun->debug code->gwtStop->gwtRun->debug code->gwtStop->gwtRun->....->edit librirary code->Gradle refresh->gwtStop->gwtRun ->

TO MANY MANUAL WORK FOR IDE ... Eclipse ;)

среда, 26 апреля 2017 г., 20:14:55 UTC+4 пользователь Gordan Krešić написал:

Works for me™ :)

I did have troubles setting up everything for the first time, but I'm still not very fluent with Gradle, so can not say how much those troubles were related to Putnami and how much to Gradle itself.

Right now, most of my build-related troubles are related to Buildship (Eclipse Gradle plugin) and not that much to Gradle (and Putnami). If you have troubles running Putnami tasks from Eclipse, try running them from command line, just to rule out Eclipse/Buildship as source of your pains.

On Wednesday, April 26, 2017 at 5:47:16 PM UTC+2, Олег Рачаев wrote:
I ask you offtop questin: how far you progress with putnami gradle plugin. I've managed to setup and work with it. But I realize more and more that gwt+gradle+putnami=pain. Sometimes i feel soo tired so I want go back to vanilla gwt+ant+eclipse plugin

четверг, 1 декабря 2016 г., 13:01:27 UTC+4 пользователь Gordan Krešić написал:
When turned ON, -incremental should "compile faster by reusing data from the previous compile". Why it is not turned on by default? Are there any caveats?

Google gives me mostly SDM related use-cases which I understand. But I'm wondering if using incremental compilation may speed up regular Gradle builds. If it matters, I'm using Putnami Gradle plugin.

GWT 2.8.1 - Could not find artifact org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1

Hi,

Thanks for the hard work about GWT 2.8.1.

Do you plan to release org.codehaus.mojo:gwt-maven-plugin:jar:2.8.1 ?

Thanks

Re: Why incremental compiler option defaults to OFF?

Works for me™ :)

I did have troubles setting up everything for the first time, but I'm still not very fluent with Gradle, so can not say how much those troubles were related to Putnami and how much to Gradle itself.

Right now, most of my build-related troubles are related to Buildship (Eclipse Gradle plugin) and not that much to Gradle (and Putnami). If you have troubles running Putnami tasks from Eclipse, try running them from command line, just to rule out Eclipse/Buildship as source of your pains.

On Wednesday, April 26, 2017 at 5:47:16 PM UTC+2, Олег Рачаев wrote:

I ask you offtop questin: how far you progress with putnami gradle plugin. I've managed to setup and work with it. But I realize more and more that gwt+gradle+putnami=pain. Sometimes i feel soo tired so I want go back to vanilla gwt+ant+eclipse plugin

четверг, 1 декабря 2016 г., 13:01:27 UTC+4 пользователь Gordan Krešić написал:
When turned ON, -incremental should "compile faster by reusing data from the previous compile". Why it is not turned on by default? Are there any caveats?

Google gives me mostly SDM related use-cases which I understand. But I'm wondering if using incremental compilation may speed up regular Gradle builds. If it matters, I'm using Putnami Gradle plugin.

Re: Why incremental compiler option defaults to OFF?

I ask you offtop questin: how far you progress with putnami gradle plugin. I've managed to setup and work with it. But I realize more and more that gwt+gradle+putnami=pain. Sometimes i feel soo tired so I want go back to vanilla gwt+ant+eclipse plugin

четверг, 1 декабря 2016 г., 13:01:27 UTC+4 пользователь Gordan Krešić написал:

When turned ON, -incremental should "compile faster by reusing data from the previous compile". Why it is not turned on by default? Are there any caveats?

Google gives me mostly SDM related use-cases which I understand. But I'm wondering if using incremental compilation may speed up regular Gradle builds. If it matters, I'm using Putnami Gradle plugin.

Re: Urgent

GWT Polymer is great as well.

https://github.com/manolo/gwt-polymer-elements

On Wednesday, April 26, 2017 at 4:14:50 AM UTC-4, Sachin Chaudhari wrote:

This is somthing simmilar in questions you may come accross.
If I am not choosing Angular JS I am choosing GWT then for cool widgets which library from google I should use. I really want cool stuff.
Thanks in advance.

Unable to add a new module to the webapp using Eclipse

Hello,

I created a sample GWT webapp using the Eclipse plugin, and it runs perfectly.

But when I try adding a new module by,

    a) Right-clicking the above webapp project,
    b) Selecting the "New | Other... | GWT Classes | Module" option; and
    c) Clicking the Next button on the wizard

nothing happens - the wizard continues to remain on the same wizard-page!

I next copy-pasted the package/directory structure of my working webapp, and made suitable changes to the 'NewModule.gwt.xml' and its contents; also changed Java class names appropriately.

But when I run GWT Compile on the project (by right clicking the project in Eclipse), it only compiles the original webapp, completely ignoring my 'NewModule' module that I manually created on the file-system.

What am I doing wrong?
Is there a command-line method to ease the process of a new module-creation in an existing web app, or, ideally, creating it as a stand-alone entity?

I'm using GWT 2.8 with Eclipse Neon, on Ubuntu 16.04.

Regards,
/HS

Re: GWT 2.8.1 release

Oh, great news!

Thanks for the effort to all the developers & contributors.

Regards

El martes, 25 de abril de 2017, 21:30:21 (UTC+2), Colin Alworth escribió:

I'm very pleased to announce the release of GWT 2.8.1. This contains many bugfixes and a few enhancements to JsInterop.

Highlights from release notes:

Re: Urgent

GWT Material Design, https://github.com/GwtMaterialDesign/gwt-material , works well for me.

Regards,

Rodolfo

On Wed, Apr 26, 2017 at 5:15 AM Sachin Chaudhari <chaudhari.sach22@gmail.com> wrote:

This is somthing simmilar in questions you may come accross.
If I am not choosing Angular JS I am choosing GWT then for cool widgets which library from google I should use. I really want cool stuff.
Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Urgent

This is somthing simmilar in questions you may come accross.

If I am not choosing Angular JS I am choosing GWT then for cool widgets which library from google I should use. I really want cool stuff.

Thanks in advance.

Re: GWT 2.8.1 release

Great! I saw it in maven central day before and was surprised:)

вторник, 25 апреля 2017 г., 23:30:21 UTC+4 пользователь Colin Alworth написал:

I'm very pleased to announce the release of GWT 2.8.1. This contains many bugfixes and a few enhancements to JsInterop.

Highlights from release notes:

Elemental1's JSON parser now correctly throws an exception when a string, object, or array is not correctly ended.

Support filtering JsInterop types for export, with whitelist/blacklist and wildcards. The -generateJsInteropExport flag is still used to enable the feature, but -includeJsInteropExport and -excludeJsInteropExport now exist to specify packages with optional * wildcards. Later arguments and patterns override earlier ones.

Support "*" (any) and "?" (unknown) types as a JsType native name. The "Unknown" type can be preferred over Object if the type is unknown, while "any" is preferred supertype of any JS type, including primitives.

Additionally, this supports the recent beta release of jsinterop.base and elemental2, available from Maven Central.

Please check out the full release notes, then download the release zip or update your project to get version 2.8.1 from Maven Central.

Tuesday, April 25, 2017

Re: Compiler error with the latest gwt head ?

The issue seems to be with usage of the new Elemental2 libraries. It looks like it has not much to do with my Java code, just the inclusion of Elemental2 breals the compile.

Switching to the old JSNI Console logging works:

@EntryPoint

public class Main {

@Inject

private Caller<Ping> ping;

@Inject

private Console console;

@AfterInitialization

private void afterInitialization() {

ping.call((String response) -> {

console.log(response);

}).ping();

}

// If I switch to this, it works

public static native void log(String message) /*-{

console.log(message);

}-*/;

}

On Tuesday, April 25, 2017 at 5:49:10 PM UTC-7, Hristo Stoyanov wrote:

:recres-client:compileJava
:recres-client:compileJava - is not incremental (e.g. outputs have changed, no previous execution, etc.).
:recres-client:processResources NO-SOURCE
:recres-client:classes
:recres-client:gwtCompile
Apr 25, 2017 5:44:22 PM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Compiling module com.recres.web.MainDev
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Computing all possible rebind results for 'org.jboss.errai.marshalling.client.api.MarshallerFactory'
Rebinding org.jboss.errai.marshalling.client.api.MarshallerFactory
Invoking generator org.jboss.errai.marshalling.rebind.MarshallersGenerator
Generating Marshallers Bootstrapper...
Checking ErraiApp.properties for configured types ...
Computing all possible rebind results for 'org.jboss.errai.ioc.client.container.IOCEnvironment'
Rebinding org.jboss.errai.ioc.client.container.IOCEnvironment
Invoking generator org.jboss.errai.ioc.rebind.ioc.bootstrapper.IOCEnvironmentGenerator
Generating Extensions Bootstrapper...
Computing all possible rebind results for 'org.jboss.errai.ioc.client.Bootstrapper'
Rebinding org.jboss.errai.ioc.client.Bootstrapper
Invoking generator org.jboss.errai.ioc.rebind.ioc.bootstrapper.IOCGenerator
generating ioc bootstrapping code...
Compiling 1 permutation
Compiling permutation 0...
[ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.
at com.google.gwt.dev.js.ast.JsVisitor.translateException(JsVisitor.java:482)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:469)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsNew.traverse(JsNew.java:71)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsReturn.traverse(JsReturn.java:51)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptWithInsertRemove(JsVisitor.java:461)
at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:53)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsFunction.traverse(JsFunction.java:181)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsExprStmt.traverse(JsExprStmt.java:42)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptWithInsertRemove(JsVisitor.java:461)
at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:53)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgramFragment.traverse(JsProgramFragment.java:41)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgram.traverse(JsProgram.java:120)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.JsSymbolResolver.execImpl(JsSymbolResolver.java:69)
at com.google.gwt.dev.js.JsSymbolResolver.exec(JsSymbolResolver.java:58)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:391)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at com.google.gwt.thirdparty.guava.common.base.Preconditions.checkNotNull(Preconditions.java:212)
at com.google.gwt.thirdparty.guava.common.collect.MapMakerInternalMap.putIfAbsent(MapMakerInternalMap.java:3521)
at com.google.gwt.thirdparty.guava.common.collect.Interners$WeakInterner.intern(Interners.java:88)
at com.google.gwt.dev.js.ast.JsNormalScope.doCreateName(JsNormalScope.java:49)
at com.google.gwt.dev.js.ast.JsScope.declareName(JsScope.java:60)
at com.google.gwt.dev.js.ast.JsScope.declareUnobfuscatableName(JsScope.java:91)
at com.google.gwt.dev.js.JsSymbolResolver$JsResolveSymbolsVisitor.resolveUnqualifiedName(JsSymbolResolver.java:51)
at com.google.gwt.dev.js.JsAbstractSymbolResolver.endVisit(JsAbstractSymbolResolver.java:54)
at com.google.gwt.dev.js.ast.JsNameRef.traverse(JsNameRef.java:113)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
... 42 more
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsNameRef
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsNew
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsReturn
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsBlock
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsFunction
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsExprStmt
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): var _, prototypesByTypeId, initFnList, PERMUTATION_NOT_SET = -1, permutationId = -1;
function getPermutationId(){
return permutationId;
}

function setGwtProperty(propertyName, propertyValue){
if (typeof window === 'object' && typeof window['$gwt'] === 'object') {
window['$gwt'][propertyName] = propertyValue;
}
}

function registerEntry(){
return registerEntry();
}

[...]

com.google.gwt.dev.js.ast.JsGlobalBlock
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgramFragment>
com.google.gwt.dev.js.ast.JsProgramFragment
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgram>
com.google.gwt.dev.js.ast.JsProgram
[ERROR] Unrecoverable exception, shutting down
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
at com.google.gwt.dev.javac.CompilationProblemReporter.logAndTranslateException(CompilationProblemReporter.java:106)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:459)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Thread.java:745)
[ERROR] Not all permutation were compiled , completed (0/1)

Re: Compiler error with the latest gwt head ?

Also present in the just release GWT 2.8.1

On Tuesday, April 25, 2017 at 5:49:10 PM UTC-7, Hristo Stoyanov wrote:

:recres-client:compileJava
:recres-client:compileJava - is not incremental (e.g. outputs have changed, no previous execution, etc.).
:recres-client:processResources NO-SOURCE
:recres-client:classes
:recres-client:gwtCompile
Apr 25, 2017 5:44:22 PM java.util.prefs.WindowsPreferences <init>
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
Compiling module com.recres.web.MainDev
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Computing all possible rebind results for 'org.jboss.errai.marshalling.client.api.MarshallerFactory'
Rebinding org.jboss.errai.marshalling.client.api.MarshallerFactory
Invoking generator org.jboss.errai.marshalling.rebind.MarshallersGenerator
Generating Marshallers Bootstrapper...
Checking ErraiApp.properties for configured types ...
Computing all possible rebind results for 'org.jboss.errai.ioc.client.container.IOCEnvironment'
Rebinding org.jboss.errai.ioc.client.container.IOCEnvironment
Invoking generator org.jboss.errai.ioc.rebind.ioc.bootstrapper.IOCEnvironmentGenerator
Generating Extensions Bootstrapper...
Computing all possible rebind results for 'org.jboss.errai.ioc.client.Bootstrapper'
Rebinding org.jboss.errai.ioc.client.Bootstrapper
Invoking generator org.jboss.errai.ioc.rebind.ioc.bootstrapper.IOCGenerator
generating ioc bootstrapping code...
Compiling 1 permutation
Compiling permutation 0...
[ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit.
at com.google.gwt.dev.js.ast.JsVisitor.translateException(JsVisitor.java:482)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:469)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsNew.traverse(JsNew.java:71)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsReturn.traverse(JsReturn.java:51)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptWithInsertRemove(JsVisitor.java:461)
at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:53)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsFunction.traverse(JsFunction.java:181)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsExprStmt.traverse(JsExprStmt.java:42)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAcceptWithInsertRemove(JsVisitor.java:461)
at com.google.gwt.dev.js.ast.JsVisitor.acceptWithInsertRemove(JsVisitor.java:121)
at com.google.gwt.dev.js.ast.JsBlock.traverse(JsBlock.java:53)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgramFragment.traverse(JsProgramFragment.java:41)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.ast.JsProgram.traverse(JsProgram.java:120)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
at com.google.gwt.dev.js.ast.JsVisitor.doAccept(JsVisitor.java:444)
at com.google.gwt.dev.js.ast.JsVisitor.accept(JsVisitor.java:109)
at com.google.gwt.dev.js.JsSymbolResolver.execImpl(JsSymbolResolver.java:69)
at com.google.gwt.dev.js.JsSymbolResolver.exec(JsSymbolResolver.java:58)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:391)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at com.google.gwt.thirdparty.guava.common.base.Preconditions.checkNotNull(Preconditions.java:212)
at com.google.gwt.thirdparty.guava.common.collect.MapMakerInternalMap.putIfAbsent(MapMakerInternalMap.java:3521)
at com.google.gwt.thirdparty.guava.common.collect.Interners$WeakInterner.intern(Interners.java:88)
at com.google.gwt.dev.js.ast.JsNormalScope.doCreateName(JsNormalScope.java:49)
at com.google.gwt.dev.js.ast.JsScope.declareName(JsScope.java:60)
at com.google.gwt.dev.js.ast.JsScope.declareUnobfuscatableName(JsScope.java:91)
at com.google.gwt.dev.js.JsSymbolResolver$JsResolveSymbolsVisitor.resolveUnqualifiedName(JsSymbolResolver.java:51)
at com.google.gwt.dev.js.JsAbstractSymbolResolver.endVisit(JsAbstractSymbolResolver.java:54)
at com.google.gwt.dev.js.ast.JsNameRef.traverse(JsNameRef.java:113)
at com.google.gwt.dev.js.ast.JsVisitor.doTraverse(JsVisitor.java:467)
... 42 more
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsNameRef
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsNew
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(23): <source info not available>
com.google.gwt.dev.js.ast.JsReturn
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsBlock
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsFunction
[ERROR] at Type_factory__e_d_MediaStreamTrackEvent__quals__j_e_i_Any_j_e_i_Default.java(22): <source info not available>
com.google.gwt.dev.js.ast.JsExprStmt
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): var _, prototypesByTypeId, initFnList, PERMUTATION_NOT_SET = -1, permutationId = -1;
function getPermutationId(){
return permutationId;
}

function setGwtProperty(propertyName, propertyValue){
if (typeof window === 'object' && typeof window['$gwt'] === 'object') {
window['$gwt'][propertyName] = propertyValue;
}
}

function registerEntry(){
return registerEntry();
}

[...]

com.google.gwt.dev.js.ast.JsGlobalBlock
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgramFragment>
com.google.gwt.dev.js.ast.JsProgramFragment
[ERROR] at com.google.gwt.dev.js.ast.JsProgram(0): <JsProgram>
com.google.gwt.dev.js.ast.JsProgram
[ERROR] Unrecoverable exception, shutting down
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
at com.google.gwt.dev.javac.CompilationProblemReporter.logAndTranslateException(CompilationProblemReporter.java:106)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:459)
at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:272)
at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:198)
at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:50)
at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:74)
at java.lang.Thread.run(Thread.java:745)
[ERROR] Not all permutation were compiled , completed (0/1)