Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST

Do you have JDT in your dependencies? (mvn dependency:tree) And do you (still) have both client and server code in the same project? Also, which gwt-maven-plugin do you use, and which version? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST

Do you have JDT in your dependencies? (mvn dependency:tree) And do you (still) have both client and server code in the same project? Also, which gwt-maven-plugin do you use, and which version? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

Re: 2.8rc1 and server reload in Intellij

Just use RC2 now, much simpler  -- 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+unsubscr...@googlegroups.com. To post to this group, send email

Re: 2.8rc1 and server reload in Intellij

Workaround would be to duplicate the class, applying the changes, and using it as the -server argument to DevMode instead of the broken one from GWT. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

Re: 2.8.0 RC1 is here!

Check your classpath, you must be downgrading the servlet API to a 2.x version: http://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletResponse.html#getHeader-java.lang.String- -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

[gwt-contrib] Re: 2.8.0 RC1 issue

FWIW, regarding the ServiceConfigurationError: https://github.com/gwtproject/gwt/issues/9343 On Saturday, August 6, 2016 at 8:38:21 PM UTC+2, Paul Stockley wrote: > > I reset my project from scratch and it is now working. There must have > been some residual stuff left from the last snapshot

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

SDM is meant to be "no optimization" (actually it was originally called Super Draft Mode). What I was suggesting was *compiling* with 0 optimization to see if that'd reproduce the issue as in SDM, which would validate the hypothesis. -- You received this message because you are subscribed to

Re: Documentation site on github

There's an icon next to the page title that leads to an online editor. That'll give you the path to the file in the repo (but it should src/main/markdown followed by the path in the URL) -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

Re: Using custom servlet for GWT-RPC with GWTTestCase

On Thursday, August 4, 2016 at 9:26:27 PM UTC+2, Kay Pac wrote: > > I guess I am confused. I understand the need to do as much testing as > possible with regular JUnit/TestNG tests, which I try to do. What I don't > understand precisely is where the area of coverage for GWTTestCase is - >

Re: System.getProperty(...) - compile vs Eclipse plug-in difference (2.8b1)

This might be due to the optimization level. What if you compile as -draft or -optimize 0? FWIW, GWT tends to get system props in static initialization of constants, passing string literals as argument. I.e. static final String PROP_VALUE = System.getProperty("myProperty"); On Thursday, August

Re: [gwt-contrib] GWT 2.8.0-rc1 issue (GWT 2.8.0-beta1 working)

Goktug: my reading of JsInterop is that @JsType(isNative=true) types shouldn't have non-annotated non-public members: either they're "mapped" properties and methods and should be public or annotated with @JsMethod or @JsProperty, or they're @JsOverlay methods; and there shouldn't be

Re: 2.8rc1 and server reload in Intellij

Reproduced. I have a fix: https://gwt-review.googlesource.com/15500 We probably need to add this ("restart web server") to our smoke test process. On Thursday, August 4, 2016 at 9:19:08 AM UTC+2, P.G.Taboada wrote: > > Hi, > > with GWT 2.8 I cannot reload the server anymore: > >

Re: [gwt-contrib] Re: Bean Validation

On Thursday, August 4, 2016 at 4:19:50 PM UTC+2, Colin Alworth wrote: > > What maven repo has the SNAPSHOT in it? > Sonatype OSSRH? https://github.com/ManfredTremmel/gwt-bean-validators/blob/4600230efb15f176f91b15d06d0ffa39bfda1feb/pom.xml#L57-L68 -- You received this message because you

Re: GWT 2.8.0-rc1 and closure compiler

On Thursday, August 4, 2016 at 2:21:29 PM UTC+2, Luis Fernando Planella Gonzalez wrote: > > I've always used the closure compiler with past versions (even with > 2.8.0-beta1, which we have used in production already). > Now, to my surprise, it is no longer supported in GWT 2.8.0-rc1, as >

Re: Using custom servlet for GWT-RPC with GWTTestCase

JUnitShell support for is not meant for integration tests. You probably shouldn't try to use it that way. Either start a separate server (using CORS), or don't use a GWTTestCase (possibly use a dedicated GWT app and drive it through Selenium/WebDriver. -- You received this message because

Re: Dev mode issue after updating to rc1

Yes, it's needed, or you'll actually have both versions in the classpath. -- 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

Re: Dev mode issue after updating to rc1

Works for me. Could it be that you forgot to override gwt-maven-plugin's dependencies? https://gwt-maven-plugin.github.io/gwt-maven-plugin/user-guide/using-different-gwt-sdk-version.html Also works well with "mvn appengine:devserver_start && mvn gwt:run-codeserver" (and "mvn

Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST

On Tuesday, August 2, 2016 at 6:35:05 PM UTC+2, Uwe Maurer wrote: > > Great that most dependencies are referenced now. > > You are right, the extra JDT library should not even be on the GWT > classpath. > We use the gwt-gradle-plugin to compile GWT projects with gradle, maybe > our

Re: GWT 2.8.0 RC1 - InternalCompilerException: Error constructing Java AST

On Tuesday, August 2, 2016 at 5:50:22 PM UTC+2, Uwe Maurer wrote: > > Thanks for the hint. Yes, the problem was that GWT SDK duplicates these > JDT classes instead of depending on the corresponding library. > JDT is the only dependency that's still bundled into GWT, and this is the case

[gwt-contrib] Re: Unable to compile GWT 2.8.0-rc1 module in IntelliJ

I actually meant the ant dependency with the test scope, but actually gwt uses a different ant dependency. But it really looks like a bug in IntelliJ now that we unbundled most dependencies from Maven artifacts. -- You received this message because you are subscribed to the Google Groups "GWT

[gwt-contrib] Re: GWT 2.8.0 RC1 is here!

This is https://github.com/gwtproject/gwt/issues/9382 and is a bug in gwt-jackson's POM. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

GWT 2.8 RC1 - Could not merge 2 super sourced packages

Try compiling with -strict to see what those 16 classes in error are. Given GWTx hasn't been updated for years, it's highly likely there's some conflicting emulated classes with modern GWT. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To

[gwt-contrib] Re: Unable to compile GWT 2.8.0-rc1 module in IntelliJ

That might be this. Do you have gwt-dev as a dependency or is it only added by IntelliJ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[gwt-contrib] Unable to compile GWT 2.8.0-rc1 module in IntelliJ

This might be caused by our unbundling of most dependencies; have you raised the issue on JetBrains' issue tracker? BTW, can you paste the classpath used by IntelliJ? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from

[gwt-contrib] Re: 2.8.0 RC1 issue

On Sunday, July 31, 2016 at 2:01:58 PM UTC+2, Paul Stockley wrote: > > The Mac project is pretty much nearly all client code. The only lib it > includes in web inf is junit. To be clear this is using the sdk version of > Gwt, not maven. Can you share the full classpath in both cases? and the

[gwt-contrib] Re: 2.8.0 RC1 issue

On Sunday, July 31, 2016 at 5:29:24 AM UTC+2, Paul Stockley wrote: > > I have a couple of different issues with the new RC1 build. On my mac > project, I get the following error when starting devmode from the initellij > debug launch config > > The code server is ready at

Re: 2.8.0 RC1 is here!

Check your dependencies, you may have Servlets API pre-3.0 (which introduced this method); either coming before Servlets API 3.1 in the classpath (they don't have the same artifactId so they could both be present), or in place of 3.1 (if javax.servlet:javax.servlet-api is somehow excluded).

Re: 2.8.0 RC1 is here!

.core.client, > com.google.gwt.core.client.impl > > > as mentioned in the workaround solve this issue. > > Am Freitag, 29. Juli 2016 16:26:14 UTC+2 schrieb Thomas Broyer: >> >> >> >> On Friday, July 29, 2016 at 1:41:33 PM UTC+2, kimi wrote: >>> >>> ok, didn&

[gwt-contrib] Re: GWT 2.8.0 RC1 is here!

I'd start with double-checking your dependencies. With 2.8 from the Central repository, most dependencies that used to be bundled into the gwt-user and gwt-dev JARs have now been unbundled and properly declared as Maven dependencies, so you may have had exclusions that now need to be removed. I

Re: 2.8.0 RC1 is here!

On Friday, July 29, 2016 at 1:41:33 PM UTC+2, kimi wrote: > > ok, didn"t know gin work with jdk7, just saw this in the release note : > https://github.com/gwtproject/gwt/issues/9311 > i'm on jdk7, guava18 and gin 2. > The thing with GIN is that it uses a custom ClassLoader to be able to "read"

Re: [gwt-contrib] Re: gwtproject.org site

On Friday, July 29, 2016 at 2:49:17 PM UTC+2, Andreas Ofner wrote: > > Hi Manuel, > > Am Freitag, 29. Juli 2016 13:47:43 UTC+2 schrieb Manuel Carrasco Moñino: >> >> About github pages with custom domains, the only minor I see is that it >> does not supports https, but currently our site is not

Re: 2.8.0 RC1 is here!

On Friday, July 29, 2016 at 12:16:30 PM UTC+2, Juan Pablo Gardella wrote: > > You could replace it with dagger2. > +1 Easier said than done though. For example, we have a lot of factories, and moving them to AutoFactory is not straightforward either (we have many factories able to provide

Re: 2.8.0 RC1 is here!

On Friday, July 29, 2016 at 11:23:41 AM UTC+2, kimi wrote: > > nice, thanx for the great work. > > the only blocking point for me now is GIN. > GIN or Java 7? Because GIN with Java 8 works (in our project I didn't even need the workaround) No, what's blocking many of use is currently Guava

[gwt-contrib] Thinking about the future: GWT 3, J2Cl, modularization, etc.

Hi all, We've talked about modularizing GWT for several years now, and I gave it a try at several occasions, with Maven, then Gradle, then Buck… and last year I completely gave up, knowing the J2Cl was coming which would be quite disruptive, with the hope that we could start on new grounds

Re: using Generics in GWT JsInterop: Uncaught java.lang.ClassCastException

On Wednesday, July 27, 2016 at 4:28:29 PM UTC+2, zakaria amine wrote: > > Hoping that the stable release will correct this issue. > The final release will likely be the same as the current SNAPSHOT, unless blockers are found in RC1 (RC1 should be the same as the current SNAPSHOT, when it

Re: Question on the open issues for 2.8 rc1

On Tuesday, July 26, 2016 at 9:55:51 PM UTC+2, P.G.Taboada wrote: > > Hi, > > I have been monitoring the issues for the rc1 (as far as milestone 2.8 in > github issues means rc1), > and it actually comes down to 4 documentation issues and > > https://github.com/gwtproject/gwt/issues/9352 >

Re: using Generics in GWT JsInterop: Uncaught java.lang.ClassCastException

On Tuesday, July 26, 2016 at 4:45:03 PM UTC+2, zakaria amine wrote: > > I have an interface annotated with @JsFunction that I use as a callback > for events. As there are different types of events, I have added a type > parameter: > > > @JsFunctionpublic interface Function{ > > public

[gwt-contrib] Re: GWT 2.8.0 SNAPSHOT fails to compile

On Friday, July 22, 2016 at 4:51:13 PM UTC+2, Kirill Prazdnikov wrote: > > >> If you see Emulation inheriting Internal, then it means you still have, >> somehow, gwt-user 2.8.0-beta1 in your classpath, along with gwt-dev >> 2.8.0-SNAPSHOT; >> > > > Hi Thomas, > > I compile my app with

[gwt-contrib] Re: GWT 2.8.0 SNAPSHOT fails to compile

On Friday, July 22, 2016 at 3:02:04 PM UTC+2, Sri Harsha Chilakapati wrote: > > I have been using GWT 2.8.0 Beta 1 till now, and my application is being > compiled successfully. But with the snapshot I'm getting a error. It is > here. > > ~~~Java > Jul 22, 2016 1:42:21 PM

Re: How to detect the scrollpanel is still scrolling or not in GWT?

I think the generally adopted pattern is to schedule a task 100 or 250ms away, and reschedule it on each scroll event (use a c.g.g.user.client.Timer to be able to reschedule it). Ideally, you'd also use a "passive event listener", but GWT doesn't expose it:

Re: [gwt-contrib] Re: GWT 2.8 RC1 Help with testing

See the README-MAVEN.txt file in each sample. One uses gwt:devmode, the other appengine:devserver_start followed by gwt:codeserver. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails

Re: How to hide page or set invisible during page loading

On Thursday, July 21, 2016 at 3:06:33 PM UTC+2, Gilberto wrote: > > Without changing the host page there's little you can do in GWT to avoid > showing the original page: the page is rendered while the GWT module itself > is loading. So you can't execute GWT code without loading it first. > >

Re: [gwt-contrib] Re: GWT 2.8 RC1 Help with testing

y if needed. >>>> >>>> >>>> https://docs.google.com/spreadsheets/d/1DmF8V3fSxN1N2UgQ9zToZz6xCwtx53lOSy8_u1xTC6Q >>>> >>>> -Brandon >>>> >>>> On Wednesday, July 20, 2016 at 1:53:36 AM UTC-7, Thomas Broyer wrote: >&

Re: [gwt-contrib] GWT 2.8 RC1 Help with testing

Please reply to the original thread: https://groups.google.com/d/topic/google-web-toolkit-contributors/WegHJlSMoos/discussion (fwiw, I already did most of the smoke tests on linux/chrome) On Wednesday, July 20, 2016 at 4:46:53 PM UTC+2, Natanael Clara wrote: > > Hi, > > We have

[gwt-contrib] Re: internal compiler error with latest SNAPSHOT

+rluble Could you set a breakpoint in JjsUtils trying to understand what causes the NPE? (what is null, which method is being processed, and what it looks like in your code) Reading the code, I wonder if

[gwt-contrib] Re: GWT 2.8 RC1 Help with testing

I'll test on Linux / Chrome. On Wednesday, July 20, 2016 at 3:09:08 AM UTC+2, Daniel Kurka wrote: > > Hi all, > > we have build the preliminary GWT 2.8.0-rc1 version and now need help with > DOA testing (making sure its not dead on arrival). > > We are currently missing testers for: > > Linux /

[gwt-contrib] Re: Current snapshots failing with JDK 7

On Sunday, July 3, 2016 at 2:30:52 PM UTC+2, Jens wrote: > > Hm maybe something like > > > https://github.com/gwtproject/gwt/commit/3586e7bc10777c7d479889a5f20927cbf2aceb97 > > is needed for SerializedLambda as well? > Revisiting this while smoke-testing pre-RC1; looks like you were right: we

Re: GWT RPC in GWT 3.0+

That section doesn't touch on "To paraphrase: we have a powerful compiler, let it do work for you, you can't get that from ." It talks about the fact the mere presence of a class in the compile classpath changes the output, and the difficulty of tracking dependencies: add an "implements X" to

“No source code is available for type”

Why are you excluding *.java files from your JAR? -- 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+unsubscr...@googlegroups.com. To post to this

Re: GWT RPC in GWT 3.0+

> The compile time argument has me scratching my head. I can't find any such argument in Daniel's blog post. The problem certainly is not compile time vs runtime, it's about global knowledge, scanning the whole compile classpath (which is slow) and assuming it'll be similar to the runtime

[gwt-contrib] Re: ListAutoBean Iterator broken in current snapshot

hich methods you want and the parameterless version > defaults to Java 7 behaviour. > > On Wednesday, July 13, 2016 at 7:37:00 AM UTC-7, Thomas Broyer wrote: >> >> +cc Colin, Goktug >> >> On Tuesday, July 12, 2016 at 12:48:58 PM UTC+2, Ross Drever wrote: >>&

[gwt-contrib] GWT 2.8 last call & help with testing

We have a regression due to Java 8 changes in c.g.g.emul and generators, that affects at least AutoBeans. I'll try to work on fixes tomorrow, Friday otherwise. I'll file (or reopen) an issue for better tracking. -- You received this message because you are subscribed to the Google Groups "GWT

Re: GWT RPC in GWT 3.0+

On Wednesday, July 13, 2016 at 5:53:20 PM UTC+2, Paul Robinson wrote: > > > On 13 Jul 2016 9:17 a.m., "Kay Pac" wrote: > > > > Will the gwt serialization mechanism used in GWT-RPC remain? GWT object > serialization has been plugged into the atmosphere (realtime >

[gwt-contrib] Re: ListAutoBean Iterator broken in current snapshot

+cc Colin, Goktug On Tuesday, July 12, 2016 at 12:48:58 PM UTC+2, Ross Drever wrote: > > Calling remove on an iterator from list within an request factory entity > proxy results in an UnsupportedOperationException. > > I have isolated it to commit 288cc03 Hide Java 8 interfaces methods to >

Re: GWT OAuth2 Open Source Release

It amounts to knowledge by the AS whether this is a confidential or public client. When registering a native app, Google knows that it can only be a public app. When registering a web app, they can assume this will be a confidential client and expect you to keep the secret, well, secret. The AS

Re: GWT OAuth2 Open Source Release

There are many many many small things that are either wrong, or inappropriate, or inappropriately described. On Thursday, July 7, 2016 at 1:22:55 AM UTC+2, Paul Mazzuca wrote: > > I thought that it might be a good idea to update the existing GWT-OAuth2 > project from 2011. I know that I have

Re: Cascading GWT Application ?

On Monday, July 11, 2016 at 5:19:28 PM UTC+2, Pierre Mineaud wrote: > > Thanks again Gilberto. >> > > I followed your recommendation but the GWT world is pretty hard at the > moment. > I followed the Ronan Quillevere's >

Re: Maven Plugin for GWT - Access Dev Mode Remotely

On Friday, July 8, 2016 at 8:41:13 PM UTC+2, N Troncoso wrote: > > I'm using the net.ltgt.gwt.maven.gwt-maven-plugin. I didn't know the > bindAddress was strickly for the mojo plugin. From what I can tell it's a > fairly common parameter for opening something to a network. > What you

Re: Website docs: incorporate gwt-maven-plugin ?

This is the tutorial, and the tutorial is written with WebAppCreator and Ant, or Eclipse, in mind. It's probably a good idea to update it to "something else" (Maven or Gradle; I'd personally prefer Gradle), but that's much broader than just JUnit. The doc for testing is at

Re: Maven Plugin for GWT - Access Dev Mode Remotely

On Friday, July 8, 2016 at 6:32:26 PM UTC+2, N Troncoso wrote: > > I need to be able to hit my dev mode machine remotely. I'm using the Maven > Plugin for GWT (tbroyer version). The standard commands don't let you hit > the remote machine at all. > > If I add -Dgwt.bindAddress=0.0.0.0 to the

Re: GWT RPC in GWT 3.0+

On Thursday, July 7, 2016 at 11:54:11 AM UTC+2, Philippe Gonze wrote: > > Totally agree. GWT 3.0 without RPC would be GWT 3.dead for many of the > current GWT developpers, > > For me GWT is "Web development based on Java expertise, with practically > no other technology implications".

Re: Failed to load resource: xxx.cache.js

On top of that, GWT 2.7 explicitly sets a "modified time" on the nocache.js that doesn't actually reflects neither the time you compiled the project nor the latest modified time of the files used for the compilation (it sets it to the modified time of the gwt.xml file). If you package your app

[gwt-contrib] Re: Bean Validation

version that would already have it removed. As soon as such a project exists, and depending on GWT's release cycle/status, this can be merged in so the side project could be used against GWT snapshots (pending the next release). On Sunday, July 3, 2016 at 12:34:32 AM UTC+2, Thomas Broyer wrote

Re: gwt material and uibinder

On Monday, July 4, 2016 at 8:58:10 AM UTC+2, Pierre Mineaud wrote: > > About maven, you're probably right. But at the moment in my enterprise, we >> are switching direction for our web development (we were on meteor, a >> javascript framework client and server side), and for all developers and

Re: [gwt-contrib] Current snapshots failing with JDK 7

em" is that it could possibly upload snapshots whose Java 8 tests are actually failing, because they wouldn't be run in the jdk7 build… But yes, we can at least try that. > > El dom., 3 jul. 2016 a las 1:07, Thomas Broyer (<t.bro...@gmail.com>) > escribió: > >>

[gwt-contrib] Re: Experimental release of Elemental2

On Sunday, July 3, 2016 at 1:18:28 PM UTC+2, Jakob Jarosch wrote: > > It seems that the deployed dependency is inconsistent. > The pom.xml says "elemental-experimental" with version "2016-06-30". > But the dependency is available as "elemental2-experimental" with version > "16-06-30". > Wow,

[gwt-contrib] Current snapshots failing with JDK 7

Hi all, Current snapshots fail with JDK 7: [INFO] [INFO]Tracing compile failure path for type 'java.util.Comparator' [INFO] [INFO] [ERROR] Errors in

[gwt-contrib] Re: Bean Validation

On Saturday, July 2, 2016 at 11:40:56 PM UTC+2, ManfredTremmel wrote: > > I've read in the 2.8rc1 release notes > that JSR 303 Bean > Validation in GWT is unmaintaned and marked as deprecated. For me, the > client and server side validation is

Re: What is happening to GWT???

On Saturday, July 2, 2016 at 4:22:28 PM UTC+2, Jens wrote: > > > As said above, Google doesn't really care about "releases", except for >> that they care enough about the community "outside" who, they know, do care >> about releases. >> > > @Thomas: And thats exactly why I think GWT will have

Re: What is happening to GWT???

On Saturday, July 2, 2016 at 5:36:58 PM UTC+2, Gilberto wrote: > > Guys, threads asking if GWT is dead/dying shouldn't appear as often as it > does. Actually they shouldn't appear at all. But they do. Something is > definitely wrong. As community we should do something. > Glad you're using

Re: What is happening to GWT???

On Saturday, July 2, 2016 at 12:29:32 PM UTC+2, Gilberto wrote: > > ... and that's a problem, at least the way it is developed now. > > GWT is a more-or-less open-source project. While it is indeed open-source > (you can look at the code), the process of developing it depends heavily on >

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

https://gwt-review.googlesource.com/15352 Tested locally by running the integration tests from my gwt-maven-plugin, which includes GWTTestCase. Notice the followup change at https://gwt-review.googlesource.com/15353: interestingly, the jdtCompilerAdapter.jar including within gwt-dev is not

Re: Questions about how the GWT obfuscation process works

On Thursday, June 30, 2016 at 11:36:19 AM UTC+2, Jens wrote: > > GWT first optimizes the Java AST, then converts it into a JavaScript AST > and optimizes it as well. Once that is done the actual obfuscation is just > a simple renaming as far as I know. > Once the optimization (aka

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

Oh, BTW, please file an issue: we must not release RC1 before this is fixed. +daniel On Thursday, June 30, 2016 at 10:46:00 AM UTC+2, Thomas Broyer wrote: > > Oops? Will fix asap. > > (how about excluding HTMLUnit as a whole? only keeping JDT bundled as > we're using a

[gwt-contrib] Re: Changes to maven dependencies makes GwtTest fail

Oops? Will fix asap. (how about excluding HTMLUnit as a whole? only keeping JDT bundled as we're using a patched version) On Wednesday, June 29, 2016 at 10:12:08 PM UTC+2, Ignacio Baca Moreno-Torres wrote: > > I'm updating the old mojo plugin and one of the IT throws this stacktrace. > I'm

GWT test case failing in dev mode due to UnableToComplete exception

It most probably comes from super-sources in one if your dependencies. The way to debug it is to set a breakpoint in CompilingClassLoader, line 1142, conditionally breaking when the package name / fully qualified class name starts with "java.", to be able to see what exact class is the culprit;

Re: GWT test case failing in dev mode due to UnableToComplete exception

There's no superdevmode for tests (yet?) -- 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+unsubscr...@googlegroups.com. To post to this group,

Re: JsInterop receipts for simple JSNI code ?

FWIW, this is tracked at https://github.com/gwtproject/gwt/issues/9364 -- 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

Re: How to debug GWT application on Eclipse

On Friday, June 24, 2016 at 11:39:22 AM UTC+2, Jens wrote: > > - Then in the tree view open 'top', open {nameOfYourApp}, open >> 127.0.0.1:9876, open "sourcemaps/{nameOfYourApp}. >> - Now you will find your original java source. If you open a java file >> here you can set a breakpoint in

Re: Exception: java.lang.NoClassDefFoundError: com/google/gwt/dev/DevMode

Your problem is different. Line 177 in DevMode.java in GWT 2.7 indicates that you're passing a -server argument to DevMode whose value references a class absent from the classpath (one possibility is using AppEngine but not having the appengine JAR in the classpath). There should be a message

Re: How to debug GWT application on Eclipse

"Classic" Dev Mode (or, as most people call it, "legacy" devmode) is deprecated and scheduled for deletion after the 2.8 release. It only works in Internet Explorer (not Edge, but works in IE11), and in really old versions of Firefox and Chrome/Chromium. The way forward is "Super Dev Mode",

Re: GWT-2.8-SNAPSHOT jar questions

On Wednesday, June 22, 2016 at 8:57:30 AM UTC+2, Hristo Stoyanov wrote: > > Another idea: > Can we create a *gwtcompile.jar* for GWT 2.8, which is basically going to > be the same as *gwt-dev.jar* , minus all jetty jars? With GWT compilation > being so slow, eliminating tons of unrelated jars

Re: Feature Detection

What about laptops with touch screens? (Surface, Chrome Pixel, etc.) Maybe the user will use the mouse primarily in those? Maybe not? I seem to remember that touch-enabled couldn't be detected, because one could also just plug a touch screen to the device while the browser is open (and a page

Re: GWT 2.8 and Guava 20

On Tuesday, June 21, 2016 at 3:59:51 PM UTC+2, Johan Falk wrote: > > While not only a GWT question, I thought this was the best place to ask. > I've got an GWT 2.7 application which is being upgraded to 2.8. I'm using > one of the latest snapshot (2.8.0-269) together with Guava >

Re: Unable to access exported JsType from JavaScript

Looking at your code, the class would be available at "blah.WebUI", but you'd have to create a new instance before your can call your method, and given how you initialize it you'd have to call onModuleLoad before that. Maybe if you make your method and all the fields 'static' that'd work;

Re: AutoBean sample not working for me?

Either that or add a method to the AutoBeanFactory taking a Person as argument to be wrapped as an AutoBean. (From memory) -- 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

Re: GWT-2.8-SNAPSHOT jar questions

On Wednesday, June 15, 2016 at 10:49:56 AM UTC+2, Jens wrote: > > If it wouldn't be a feature RequestFactory depends on > Oh, you're right, the Editor Framework depends on javax.validation.ConstraintViolation but doesn't implement it so one could probably have 1.1.0.Final in classpath without

Re: GWT-2.8-SNAPSHOT jar questions

On Wednesday, June 15, 2016 at 6:42:11 AM UTC+2, Hristo Stoyanov wrote: > > Hi all, > I have a couple of questions regarding GWT 2.8 SNAPSHOT: > > *1. Why am I picking up tons of jetty libraries for doing a simple gwt > compilation? I could understand the need for the Jetty jars, if I was >

Re: JsInterop and Java collections?

On Tuesday, June 7, 2016 at 12:58:53 AM UTC+2, Thomas Broyer wrote: > > > > On Monday, June 6, 2016 at 9:15:43 PM UTC+2, Hristo Stoyanov wrote: >> >> Kirrill, >> I did not suggest to *convert*, but *map*. That means that if/when a >> JSInter-oped class is ex

Re: [gwt-contrib] Re: GWT 2.8 rc1 work items

On Monday, June 13, 2016 at 11:37:05 AM UTC+2, Daniel Kurka wrote: > > Also keep in mind that we need a green build before cutting RC1 in open > source (and this only runs daily), so we should not be merging lots of > patches at the last minute. > Maybe we could change it to run twice a day

Re: Newbie Help - how to retrieve data from another website?

On Monday, June 13, 2016 at 9:40:34 AM UTC+2, Hans Dampf wrote: > > Hi everyone, > > opening an URL like http://randomserver.com/file?get=randomXML returns a > XML-file. I don't have access to the server. > Now i am trying to receive this data and give it out in my gwt-app. > I have tried

[gwt-contrib] Re: GWT 2.8 rc1 work items

On Wednesday, June 8, 2016 at 11:06:26 AM UTC+2, Daniel Kurka wrote: > > Hi all, > > in the last steering committee meeting we agreed that making the next > version of Guava work (which contains a lot of Java8 usage) was the goal > for RC1. > > We have gotten significantly closer to this now

Re: GWT Servlet - How can I get rid of /app prefix in my requests?

On Sunday, June 12, 2016 at 2:08:35 PM UTC+2, Stefan Falk wrote: > > I don't know why but all requests are forcing me to to map each Servlet to > something like > > > > xsrf > /app/xsrf > > > > whatever > /app/whatever > > > > and so on. I can't find anything that is actually setting the

Re: Issues with GWT 2.8 snapshot

The change in review is NOT about a broken build, it's only about too much logging. It's NOT related to your issue, which still needs to be investigated on your side (why is a javadoc task looking into gwt-user?) -- You received this message because you are subscribed to the Google Groups "GWT

Re: Issues with GWT 2.8 snapshot

Also, it addresses Filipe's issue, but Hristo's one is different (and if you ask me, not actually a problem with GWT; not until proven otherwise): why does a javadoc task look at source files in gwt-user? -- You received this message because you are subscribed to the Google Groups "GWT Users"

Re: JsInterop and Java collections?

On Friday, June 10, 2016 at 11:12:27 AM UTC+2, Kirill Prazdnikov wrote: > > Hi Thomas > > Lets forget about java.util, what about simple arrays ? > > It seems that we already have java [] array -> JS Array marshalling. > And It would be very nice if we had these type of marshalling with zero

Re: JsInterop and Java collections?

Except that there is NO marshaling! There are so many cases where it just won't work that it's not even worth trying if you ask me.You need to think about isNative vs. "exported" types, method return values vs. parameters vs. fields (which can be both get and set); object identities (calling

Re: Measuring effect of using GWT features on compile time

No, SpeedTracerLogger is the internal API that routes events to either (or both) DashboardNotifier or a SpeedTracer file. -- 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

Re: Measuring effect of using GWT features on compile time

Isn't DashboardNotifier called by SpeedTracerLogger? -- 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+unsubscr...@googlegroups.com. To post to

Re: Issues with GWT 2.8 snapshot

a -version > java version "1.8.0_92" > Java(TM) SE Runtime Environment (build 1.8.0_92-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) > > $ ant -version > Apache Ant(TM) version 1.9.7 compiled on April 9 2016 > > On Thursday, June 9, 20

<    4   5   6   7   8   9   10   11   12   13   >