Re: GWT 2.8.1 release

2017-06-29 Thread Max F
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 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/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) has the same issue.
>>>
>>> On Wednesday, June 28, 2017 at 3:42:49 PM UTC+3, Thomas Broyer wrote:



 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 instead of -includeJsInteropExport.
>

 Thanks, I just fixed the release notes: 
 https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
 But the -generateJsInteropExports help message references the other two 
 as singular instead of plural: 
 https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
  

> But even then I did not succeed; CodeServer returns with:
>
> Unknown argument: -includeJsInteropExports a.b.c
>

 How are you passing the arguments?
 It looks like you're passing "-includeJsInteropExports a.b.c" as a 
 single argument, which indeed won't work. You need to pass 2 arguments: 
 "-includeJsInteropExports" and "a.b.c".

>

-- 
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@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: GWT 2.8.1 release

2017-06-29 Thread Thomas Broyer


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 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@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: GWT 2.8.1 release

2017-06-29 Thread 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 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/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) has the same issue.
>>
>> On Wednesday, June 28, 2017 at 3:42:49 PM UTC+3, Thomas Broyer wrote:
>>>
>>>
>>>
>>> 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 instead of -includeJsInteropExport.

>>>
>>> Thanks, I just fixed the release notes: 
>>> https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
>>> But the -generateJsInteropExports help message references the other two 
>>> as singular instead of plural: 
>>> https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
>>>  
>>>
 But even then I did not succeed; CodeServer returns with:

 Unknown argument: -includeJsInteropExports a.b.c

>>>
>>> How are you passing the arguments?
>>> It looks like you're passing "-includeJsInteropExports a.b.c" as a 
>>> single argument, which indeed won't work. You need to pass 2 arguments: 
>>> "-includeJsInteropExports" and "a.b.c".
>>>


-- 
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@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: GWT 2.8.1 release

2017-06-29 Thread Thomas Broyer
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/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) has the same issue.
>
> On Wednesday, June 28, 2017 at 3:42:49 PM UTC+3, Thomas Broyer wrote:
>>
>>
>>
>> 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 instead of -includeJsInteropExport.
>>>
>>
>> Thanks, I just fixed the release notes: 
>> https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
>> But the -generateJsInteropExports help message references the other two 
>> as singular instead of plural: 
>> https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
>>  
>>
>>> But even then I did not succeed; CodeServer returns with:
>>>
>>> Unknown argument: -includeJsInteropExports a.b.c
>>>
>>
>> How are you passing the arguments?
>> It looks like you're passing "-includeJsInteropExports a.b.c" as a single 
>> argument, which indeed won't work. You need to pass 2 arguments: 
>> "-includeJsInteropExports" and "a.b.c".
>>
>>>

-- 
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@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: GWT 2.8.1 release

2017-06-29 Thread Alexander Leshkin
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) has the same issue.

On Wednesday, June 28, 2017 at 3:42:49 PM UTC+3, Thomas Broyer wrote:
>
>
>
> 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 instead of -includeJsInteropExport.
>>
>
> Thanks, I just fixed the release notes: 
> https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
> But the -generateJsInteropExports help message references the other two as 
> singular instead of plural: 
> https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
>  
>
>> But even then I did not succeed; CodeServer returns with:
>>
>> Unknown argument: -includeJsInteropExports a.b.c
>>
>
> How are you passing the arguments?
> It looks like you're passing "-includeJsInteropExports a.b.c" as a single 
> argument, which indeed won't work. You need to pass 2 arguments: 
> "-includeJsInteropExports" and "a.b.c".
>
>>

-- 
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@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: GWT 2.8.1 release

2017-06-29 Thread Max F
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:
>>
>> 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 -codeServerPort 9997 -port  
>> -generateJsInteropExports -includeJsInteropExports a.b.c -war 
>> D:\XXX\XXX\war com.XXX.XXX.XXX
>>
>
> Check that this is a "real" space character (U+0020) then and not a 
> non-breaking space or other flavor? (I'm out of ideas)
>

-- 
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@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: GWT 2.8.1 release

2017-06-28 Thread Thomas Broyer


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_remote_ui_server_port}:${unique_id}" -startupUrl XXX.html 
> -logLevel INFO -codeServerPort 9997 -port  -generateJsInteropExports 
> -includeJsInteropExports a.b.c -war D:\XXX\XXX\war com.XXX.XXX.XXX
>

Check that this is a "real" space character (U+0020) then and not a 
non-breaking space or other flavor? (I'm out of ideas)

-- 
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@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: GWT 2.8.1 release

2017-06-28 Thread Max F
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 -codeServerPort 9997 -port  -generateJsInteropExports 
-includeJsInteropExports a.b.c -war D:\XXX\XXX\war com.XXX.XXX.XXX

Not using any quotes; they seem to get eliminated from the arguments string 
anyway by Eclipse.

Kind regards,
Max

Am Mittwoch, 28. Juni 2017 14:42:49 UTC+2 schrieb Thomas Broyer:
>
>
>
> 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 instead of -includeJsInteropExport.
>>
>
> Thanks, I just fixed the release notes: 
> https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
> But the -generateJsInteropExports help message references the other two as 
> singular instead of plural: 
> https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
>  
>
>> But even then I did not succeed; CodeServer returns with:
>>
>> Unknown argument: -includeJsInteropExports a.b.c
>>
>
> How are you passing the arguments?
> It looks like you're passing "-includeJsInteropExports a.b.c" as a single 
> argument, which indeed won't work. You need to pass 2 arguments: 
> "-includeJsInteropExports" and "a.b.c".
>
>>

-- 
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@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: GWT 2.8.1 release

2017-06-28 Thread Thomas Broyer


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 instead of -includeJsInteropExport.
>

Thanks, I just fixed the release 
notes: 
https://github.com/gwtproject/gwt-site/commit/54403382872815bb4ee94224839b0dbeccad8935
But the -generateJsInteropExports help message references the other two as 
singular instead of 
plural: 
https://github.com/gwtproject/gwt/blob/2.8.1/dev/core/src/com/google/gwt/dev/util/arg/ArgHandlerGenerateJsInteropExports.java#L32
 

> But even then I did not succeed; CodeServer returns with:
>
> Unknown argument: -includeJsInteropExports a.b.c
>

How are you passing the arguments?
It looks like you're passing "-includeJsInteropExports a.b.c" as a single 
argument, which indeed won't work. You need to pass 2 arguments: 
"-includeJsInteropExports" and "a.b.c".

>

-- 
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@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: GWT 2.8.1 release

2017-06-28 Thread Max F
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 returns with:

Unknown argument: -includeJsInteropExports a.b.c
Google Web Toolkit 2.8.1

Could anyone provide a working CodeServer parameters list using that 
feature? I just found the GWT test case 
(https://github.com/gwtproject/gwt/blob/master/dev/core/test/com/google/gwt/dev/ArgHandlerFilterJsInteropExportsTest.java).

Or is this feature only to be used in deployment, not during development 
using CodeServer?

Thanks for any response.

Kind regards,
Max


Am Dienstag, 25. April 2017 21:30:21 UTC+2 schrieb 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.
>

-- 
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@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: GWT 2.8.1 release

2017-06-08 Thread Ignacio Baca Moreno-Torres
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-friendly and type safe API (manual work) over raw
elemental2 https://github.com/hal/elemento (code example here
https://github.com/ibaca/rxtodo-gwt/blob/master/src/main/java/todo/client/ApplicationElement.java#L53),
IMO pretty promising! RxGWT will be using elemento typed events to make it
also Rx typed events just over elemental2!

Code example here, this is always nice...

root = li().data(ITEM, item.id).css("completed", item.completed)
.add(div().css("view")
.add(toggle =
input(checkbox).css("toggle").checked(item.completed).asElement())
.add(msg = label().textContent(item.text).asElement())
.add(destroy = button().css("destroy").asElement()))
.add(summary = input(text).css("edit").asElement())
.asElement();

bind(toggle, change, ev -> {
root.classList.toggle("completed", toggle.checked);
repository.complete(item, toggle.checked);
application.update();
});

All these fields are typed so, root is a HTMLLiElement, toggle is a
HTMLInputElement or ev in the bind method is an InputEvent.

On Wed, Jun 7, 2017 at 10:14 PM Vassilis Virvilis  wrote:

> 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 evolving the API. So no you can't use
> __this__ in __production__.
>
> Or maybe this a bad idea that will lead to a new KDE4 fiasco.
>
> Who knows?
>
> Vassilis
>
>
> On Wed, Jun 7, 2017 at 10:14 PM, Daniel Kurka 
> wrote:
>
>> 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
>> want to be part of evolving them and turning them into a finished and
>> polished product, you can do that.
>>
>> We will announce them broadly once we consider them ready for general use
>> and have a compatibility guarantee in place.
>>
>> On Wed, Jun 7, 2017 at 11:48 AM Vassilis Virvilis 
>> wrote:
>>
>>> 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 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 "complete
 enough to be reviewed and used".

 On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:
>
> 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 :-)
>
>  Vassilis
>
> On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth 
> wrote:
>
>> 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
 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
>>> 
>>> )?
>>>
>>> Thanks for all your amazing work.
>>>
>> --
 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@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: GWT 2.8.1 release

2017-06-07 Thread Vassilis Virvilis
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 evolving the API. So no you can't use
__this__ in __production__.

Or maybe this a bad idea that will lead to a new KDE4 fiasco.

Who knows?

Vassilis


On Wed, Jun 7, 2017 at 10:14 PM, Daniel Kurka 
wrote:

> 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
> want to be part of evolving them and turning them into a finished and
> polished product, you can do that.
>
> We will announce them broadly once we consider them ready for general use
> and have a compatibility guarantee in place.
>
> On Wed, Jun 7, 2017 at 11:48 AM Vassilis Virvilis 
> wrote:
>
>> 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 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 "complete
>>> enough to be reviewed and used".
>>>
>>> On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:

 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 :-)

  Vassilis

 On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth 
 wrote:

> 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
>>> 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
>> 
>> )?
>>
>> Thanks for all your amazing work.
>>
> --
>>> 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@googlegroups.com
>>> .
>>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Vassilis Virvilis
>>
>> --
>> 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@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vassilis Virvilis

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Daniel Kurka
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
want to be part of evolving them and turning them into a finished and
polished product, you can do that.

We will announce them broadly once we consider them ready for general use
and have a compatibility guarantee in place.

On Wed, Jun 7, 2017 at 11:48 AM Vassilis Virvilis  wrote:

> 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 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 "complete
>> enough to be reviewed and used".
>>
>> On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:
>>>
>>> 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 :-)
>>>
>>>  Vassilis
>>>
>>> On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth  wrote:
>>>
 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 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
> 
> )?
>
> Thanks for all your amazing work.
>
 --
>> 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@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Vassilis Virvilis
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 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 "complete
> enough to be reviewed and used".
>
> On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:
>>
>> 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 :-)
>>
>>  Vassilis
>>
>> On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth  wrote:
>>
>>> 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 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
 
 )?

 Thanks for all your amazing work.

>>> --
> 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vassilis Virvilis

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Colin Alworth
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 "complete 
enough to be reviewed and used".

On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:
>
> 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 :-)
>
>  Vassilis
>
> On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth  > wrote:
>
>> 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 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 
>>> 
>>> )?
>>>
>>> Thanks for all your amazing work.
>>>
>>

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Vassilis Virvilis
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 :-)

 Vassilis

On Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth  wrote:

> 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 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
>> 
>> )?
>>
>> Thanks for all your amazing work.
>>
> --
> 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@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Vassilis Virvilis

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Colin Alworth
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 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 
> 
> )?
>
> Thanks for all your amazing work.
>

-- 
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@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: GWT 2.8.1 release

2017-06-07 Thread Bruno Salmon


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

)?

Thanks for all your amazing work.

-- 
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@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: GWT 2.8.1 release

2017-05-15 Thread Marteijn Nouwens
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)
[INFO]  at com.google.gwt.dev.Compiler.main(Compiler.java:125)
[INFO] Caused by: java.lang.NoClassDefFoundError: 
com/google/gwt/user/rebind/rpc/BlacklistTypeFilter$RpcBlacklist
[INFO]  at 
com.google.gwt.user.rebind.rpc.BlacklistTypeFilter.(BlacklistTypeFilter.java:66)
[INFO]  at 
com.google.gwt.user.rebind.rpc.ProxyCreator.create(ProxyCreator.java:282)
[INFO]  at 
com.google.gwt.user.rebind.rpc.ServiceInterfaceProxyGenerator.generateIncrementally(ServiceInterfaceProxyGenerator.java:67)
[INFO]  at 
com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:739)
[INFO]  at 
com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:103)
[INFO]  at 
com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:78)
[INFO]  at 
com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:262)
[INFO]  at 
com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:251)
[INFO]  at 
com.google.gwt.dev.PrecompilationContextCreator$1.getAllPossibleRebindAnswers(PrecompilationContextCreator.java:86)

BUt that class is present. Anybody an idea on what could be causing this?

Marteijn

Op dinsdag 25 april 2017 21:30:21 UTC+2 schreef 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.
>

-- 
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@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: GWT 2.8.1 release

2017-05-04 Thread Bogdan Petridean
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@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: GWT 2.8.1 release

2017-04-27 Thread Eric Nissan
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.
>

-- 
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@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: [gwt-contrib] Re: GWT 2.8.1 release

2017-04-26 Thread David
I migrated my code immediatly (including the beta release of Elemental2)

Seems to work fine so far.

On Wed, 26 Apr 2017 at 14:18, Matic Petek  wrote:

> Thank you very much for this.
>
>
> On Tuesday, April 25, 2017 at 9:30:20 PM UTC+2, 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.
>>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/472fb8cf-54da-495a-95ee-fdfeb06a88cc%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW32o0Lnuw%3DaxHswWpwaF4KFBQBPHnhhpxCY%3Dxgse5RUjw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] Re: GWT 2.8.1 release

2017-04-26 Thread Matic Petek
Thank you very much for this.

On Tuesday, April 25, 2017 at 9:30:20 PM UTC+2, 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.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/472fb8cf-54da-495a-95ee-fdfeb06a88cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GWT 2.8.1 release

2017-04-26 Thread Asier
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:
>
>

-- 
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@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: GWT 2.8.1 release

2017-04-26 Thread Олег Рачаев
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.
>

-- 
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@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: [gwt-contrib] Re: GWT 2.8.1 release

2017-04-25 Thread Peter Donald
Indeed - great work!

On Wed, Apr 26, 2017 at 6:44 AM, Predrag Remark 
wrote:

> Great news!
>
> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/cebc800a-92b6-
> 4a0d-87ce-e759f645be2e%40googlegroups.com
> 
> .
>
> 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 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc4fwTkUCFyGhVTX4c%3Dpygnp8c2gBscMH_7QfisWKqfrzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] Re: GWT 2.8.1 release

2017-04-25 Thread Predrag Remark
Great news!

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/cebc800a-92b6-4a0d-87ce-e759f645be2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] GWT 2.8.1 release

2017-04-25 Thread 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.

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1a96667b-6e36-400d-a329-da0680d7d320%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


GWT 2.8.1 release

2017-04-25 Thread 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.

-- 
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@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-contrib] Re: GWT 2.8.1 release testers required!

2017-04-24 Thread Hristo Stoyanov
Colin,
How does one reference this version in Maven/Gradle projects: HEAD-SNAPSHOT 
or 2.8.1-SNPASHOT? The later seems pretty old (November 216)? Thanks.


On Thursday, April 13, 2017 at 4:51:08 PM UTC-7, Colin Alworth wrote:
>
> We're about ready to release GWT 2.8.1, a bugfix release a variety of 
> issues, including getting a stable release out that works with the new 
> jsinterop.base and elemental2 beta jars. I will need some help in 
> validating this release on our supported platforms, please contact me if 
> you are available to spend a little time testing over the next few days, 
> and I'll get the ball rolling.
>
> Thanks,
> Colin
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/0d26e69f-d5ee-46f3-9fd1-7a4466e86957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[gwt-contrib] GWT 2.8.1 release testers required!

2017-04-13 Thread Colin Alworth
We're about ready to release GWT 2.8.1, a bugfix release a variety of 
issues, including getting a stable release out that works with the new 
jsinterop.base and elemental2 beta jars. I will need some help in 
validating this release on our supported platforms, please contact me if 
you are available to spend a little time testing over the next few days, 
and I'll get the ball rolling.

Thanks,
Colin

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/350e53ba-2148-497c-8d58-eeb9528b7b6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.