Re: GWT 2.8.1 release

Thanks Alexander. Nice Am Donnerstag, 29. Juni 2017 13:59:58 UTC+2 schrieb Alexander Leshkin: > > Issue https://github.com/gwtproject/gwt/issues/9533 > > I'll create a patch. > > On Thursday, June 29, 2017 at 2:15:19 PM UTC+3, Thomas Broyer wrote: >> >> You're right! >> >> Could one of you file

Re: GWT 2.8.1 release

On Thursday, June 29, 2017 at 1:59:58 PM UTC+2, Alexander Leshkin wrote: > > Issue https://github.com/gwtproject/gwt/issues/9533 > > I'll create a patch. > Great! -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group an

Re: GWT 2.8.1 release

Issue https://github.com/gwtproject/gwt/issues/9533 I'll create a patch. On Thursday, June 29, 2017 at 2:15:19 PM UTC+3, Thomas Broyer wrote: > > You're right! > > Could one of you file an issue and/or send in a patch? > http://www.gwtproject.org/makinggwtbetter.html > > On Thursday, June 29, 201

Re: GWT 2.8.1 release

You're right! Could one of you file an issue and/or send in a patch? http://www.gwtproject.org/makinggwtbetter.html On Thursday, June 29, 2017 at 12:08:55 PM UTC+2, Alexander Leshkin wrote: > > Looks like there is a bug in > https://github.com/gwtproject/gwt/blob/a90832fec9a56f4cb83ed009c7048e0a

Re: GWT 2.8.1 release

Looks like there is a bug in https://github.com/gwtproject/gwt/blob/a90832fec9a56f4cb83ed009c7048e0a8d196fe8/dev/core/src/com/google/gwt/dev/shell/SuperDevListener.java#L175 I think it should be: args.add("-includeJsInteropExports"); args.add(regex); And line above (for excludeJsInteropExports)

Re: GWT 2.8.1 release

Hi Thomas, yes, I used a common space. The parameters keep joined as one. I'll just be waiting until someone else tries this feature. Thanks! Kind regards, Max Am Mittwoch, 28. Juni 2017 18:22:32 UTC+2 schrieb Thomas Broyer: > > > > On Wednesday, June 28, 2017 at 4:55:55 PM UTC+2, Max F wrote:

Re: GWT 2.8.1 release

On Wednesday, June 28, 2017 at 4:55:55 PM UTC+2, Max F wrote: > > Thanks for your reply, Thomas. > > I am using Brandon's Eclipse plugin. I thought a space would be a > separator for parameters; this is working for e.g. the -war parameter. My > arguments for the CodeServer: > -remoteUI "${gwt_r

Re: GWT 2.8.1 release

Thanks for your reply, Thomas. I am using Brandon's Eclipse plugin. I thought a space would be a separator for parameters; this is working for e.g. the -war parameter. My arguments for the CodeServer: -remoteUI "${gwt_remote_ui_server_port}:${unique_id}" -startupUrl XXX.html -logLevel INFO -cod

Re: GWT 2.8.1 release

On Wednesday, June 28, 2017 at 1:04:12 PM UTC+2, Max F wrote: > > Hello, > > first of all, thanks for GWT! > I am trying to make use of the new includeJsInteropExports flag while > using the CodeServer. > It seems that those new two switches need an extra "s": e.g. > -includeJsInteropExports in

Re: GWT 2.8.1 release

Hello, first of all, thanks for GWT! I am trying to make use of the new includeJsInteropExports flag while using the CodeServer. It seems that those new two switches need an extra "s": e.g. -includeJsInteropExports instead of -includeJsInteropExport. But even then I did not succeed; CodeServer r

Re: GWT 2.8.1 release

This is a programmatic mapping from closure externs https://github.com/google/closure-compiler/tree/master/contrib/externs so, at the end if it changes it will change the same in every place, so fixing it should not be very difficult. Anyways, this super awesome project 😜 is going to expose a user-

Re: GWT 2.8.1 release

thanks for the clarification. Maybe a sufficiently strong wording in the compatibility guarantees is enough. Something like this: We will try really hard to not rename all methods and move all packages around in the next week commits. However we may introduce incompatible changes as we are evolvi

Re: GWT 2.8.1 release

There is some reasoning behind us not broadly announcing elemental2 and the jsinteorp generator: They are both still beta software in the sense that we know there are existing problems, but we already want feedback on them. There are still no guarantees on APIs / compat but if you are brave and wan

Re: GWT 2.8.1 release

Ah yes that explains it. It was j2cl that I remembered. Thanks for the clarification. Vassilis On Wed, Jun 7, 2017 at 9:40 PM, Colin Alworth wrote: > I think you may be misremembering - the jars were released to maven as > experimental last summer, then as beta in April, and only after tha

Re: GWT 2.8.1 release

I think you may be misremembering - the jars were released to maven as experimental last summer, then as beta in April, and only after that were they on github. J2CL is not expected to be dropped until it is "ready", but as with elemental2, this isn't going to mean "bugfree" but more like "comp

Re: GWT 2.8.1 release

Looks like they are also here in source form https://github.com/google/elemental2 https://github.com/google/jsinterop-generator I thought google didn't want to release them before they were "ready". So either they changed their mind, or they feel it is ready or I don't remember correctly :-)

Re: GWT 2.8.1 release

The groupId has changed - using the mvnrepository site, try https://mvnrepository.com/artifact/com.google.elemental2 to see all of the jars now available. On Wednesday, June 7, 2017 at 11:14:33 AM UTC-5, Bruno Salmon wrote: > > > >> Additionally, this supports the recent beta release of jsintero

Re: GWT 2.8.1 release

> > Additionally, this supports the recent beta release of jsinterop.base and > elemental2, available from Maven Central. > > > Where can we find that elemental2 beta release (I can see only the June 2016 version on that page

Re: GWT 2.8.1 release

After upgrading to 2.8.1 i get the folling error: [INFO] at com.google.gwt.dev.Compiler$1.run(Compiler.java:118) [INFO] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55) [INFO] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50) [

Re: GWT 2.8.1 release

Great! -- 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 to google-web-toolkit@goog

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.jav

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. > > > Highligh

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 relea

GWT 2.8.1 release

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. -