Re: GWT 2.9.0 release

[Ahmad Bawaneh]

I forget to mention the generated project also include dominno-ui 
dependency, if you dont want it you can remove it, but it gives you the 
chance to test many of the GWT3/J2CL migrated modules.
and for quick support you can reach us at dominokit gitter channel  
or gwt gitter channel 


On Friday, May 15, 2020 at 1:33:17 AM UTC+3, Ahmad Bawaneh wrote:
>
> You can use domino-cli  to 
> create a j2cl simple maven project, download and the proper package for 
> your operating system from the releases page 
> , then from the command 
> line use the following command
>
> dominokit gen app -t basic --j2cl -n sample -g com.foo
>
>
> where sample is the name/artifactId of the generated project and com.foo 
> is the group id
>
> the generated project is similar to a generated GWT project from tbroyer 
> archetype.
>
> after the project is generated inside the root folder do 
> mvn clean install
>
> once the project is built you can run it in development mode 
>
> in one terminal run 
> mvn tomcat7:run -pl *-server -am -Denv=dev
>
> to start the server
>
> and in another terminal run
>
> mvn j2cl:watch
>
> access the running application from the browser through 
> http://localhost:8080/
>
> Happy J2CLing
>
> On Thursday, May 14, 2020 at 7:55:33 PM UTC+3, Robin Roos wrote:
>>
>> Congratulations on the release of 2.9.0.
>>
>> Can anyone point me to a sample Maven pom.xml from which to begin a new 
>> GWT project?  I specifically want to be using J2CL, and I'm happy to use 
>> snapshot releases if required.  Thanks, Robin.
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/51efb6dc-7ad3-43bb-8b8c-3eefd84a2aaa%40googlegroups.com.

Re: GWT 2.9.0 release

[Ahmad Bawaneh]

You can use domino-cli  to create 
a j2cl simple maven project, download and the proper package for your 
operating system from the releases page 
, then from the command 
line use the following command

dominokit gen app -t basic --j2cl -n sample -g com.foo


where sample is the name/artifactId of the generated project and com.foo is 
the group id

the generated project is similar to a generated GWT project from tbroyer 
archetype.

after the project is generated inside the root folder do 
mvn clean install

once the project is built you can run it in development mode 

in one terminal run 
mvn tomcat7:run -pl *-server -am -Denv=dev

to start the server

and in another terminal run

mvn j2cl:watch

access the running application from the browser through 
http://localhost:8080/

Happy J2CLing

On Thursday, May 14, 2020 at 7:55:33 PM UTC+3, Robin Roos wrote:
>
> Congratulations on the release of 2.9.0.
>
> Can anyone point me to a sample Maven pom.xml from which to begin a new 
> GWT project?  I specifically want to be using J2CL, and I'm happy to use 
> snapshot releases if required.  Thanks, Robin.
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2db959e7-a760-4b31-adec-37a4e23b6856%40googlegroups.com.

Re: GWT 2.9.0 release

[Michael Angueira]

Thanks so much.

On Wednesday, May 13, 2020 at 11:40:25 PM UTC-4, Colin Alworth wrote:
>
> Today we are pleased to announce the next release of GWT, version 2.9.0. 
> Some highlights of this release:
>  * GWT supports Java 9, 10, 11 language features.
>  * The elemental2 1.0.0 release is supported, along with 
> jsinterop-annotations 2.0.0 (except @JsAsync, which requires dropping 
> support for older browsers, and @JsEnum, which assumes closure-compiler 
> semantics, so isn't appropriate for GWT2), bringing GWT2 in line with J2CL. 
> Since this is now an official stable release of elemental2, the JSNI-based 
> elemental that is included with GWT is deprecated, and will be removed in a 
> future release.
>  * The release was tested on a variety of operating systems, on Java 8, 
> 11, and 14. Java 7 is no longer officially supported, and future builds 
> will be compiled for Java 8 as the minimum required version.
>
>
> Starting shortly after this release, we're going to be changing the 
> release process slightly - there will be more frequent dated releases 
> (something like 2.9-20200701) that occur every few months, and minor/bug 
> fix releases that happen intermittently to signify that a more lengthy 
> manual testing and acceptance process has taken place. The idea is that 
> with more frequent releases, changes will make their way faster to the 
> developers that want them, while for others, more heavily tested releases 
> for maintenance-mode projects will still be available.
>
> We'll also be talking soon on the contributors list about the upcoming 
> releases of individual projects that represent the various modules found in 
> gwt-user.jar, updated and tested for use in either GWT2 or J2CL.
>
> We're experiencing some issues in updating the gwtproject.org website, 
> but to get this release out while that is managed, find the zip download 
> and the release notes below. Maven/Gradle/Ivy users, just update the GWT 
> SDK versions to 2.9.0 - the various plugins will be updated as needed in 
> the coming days.
>
> GWT SDK zip download: 
> https://storage.googleapis.com/gwt-releases/gwt-2.9.0.zip
>
> 
>
> Release Notes for 2.9.0:
>
> Highlights
>
>- Able to compile projects with jsinterop-base 1.0.0, elemental2 
>1.0.0, and jsinterop-annotations 2.0.0. With the exception of @JsAsync and 
>@JsEnum, this brings GWT2 to be compatible across these tools with J2CL.
>- Added support for Java language levels 9, 10, and 11.
>- Officially, support is dropped for running the GWT compiler or 
>server-side tooling on Java 7. The GWT distribution is still compiled to 
>run on Java 7 for this release, but no guarantees are made about whether 
> or 
>not this will work. Future versions will compile bytecode for Java 8+. The 
>release was tested and found to work cross platform when run with Java 8, 
>11, and 14.
>
>
> Deprecations
>
>- Elemental has been officially deprecated - it is still included in 
>this release, but may not appear in future releases. Instead, we encourage 
>the use of the Elemental2 libraries, which are compatible with both GWT2 
>and J2CL.
>- Removed NoSuchMethodException emulation.
>
>
> Bug fixes
>
>- Fixes Arrays.binarySearch semantics for float[] and double[]
>- Adds Support multi-line messages in errors/exceptions
>- Adds shutdown hook in DiskCache to clean up temp files
>- Cache Gecko version to lower CPU usage on FireFox
>- Do not assume that "this" is always non null.
>- Updates globals for Firefox version 60.0.2, Chrome 66.0.3359.45
>- Fixes String.regionMatches.
>- Native JsMethods allowed to coexist with implementations with the 
>same name.
>- Make sure lambdas box, unbox and insert erasure casts when necessary.
>- Negative zero treated properly in Double/Float.compare()
>
>
> Miscellaneous
>
>- Updates CLDR to version 34.
>- Arrays now implement Cloneable
>- Link backing errors together with a cause attribute, start tracking 
>suppressed errors in addition to the cause in underlying error object.
>- Add AtomicReference to gwt/emul.
>- Propagate script nonces via ScriptInjector
>- Add partial emulation for ExecutorService and 
>ScheduledExecutorService
>- Emulate java.util.concurrent.Flow
>- Emulate javax.annotation{,.processing}.Generated
>- Make sure "goog.global" is $wnd if not defined.
>- Add when-linker-added element definition
>- Add Reader and StringReader emulation.
>- Remove GWT version check.
>- Do not show "unusable-by-js" warning for synthetic methods.
>- Update unmodifiableList to throw on Java8 methods.
>- Disable DataflowOptimizer by default and emit a warning when used
>
> For more detail, see the commit log 
> .
>
>
> 
>
> Finally, if you haven't already done so, please join the very active GWT 
> discussions happening at https:

Re: GWT 2.9.0 release

[Robin Roos]

Congratulations on the release of 2.9.0.

Can anyone point me to a sample Maven pom.xml from which to begin a new GWT 
project?  I specifically want to be using J2CL, and I'm happy to use 
snapshot releases if required.  Thanks, Robin.


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f1f2e7b2-39a8-4a05-b621-7a35ee021512%40googlegroups.com.

Re: GWT 2.9.0 release

[Adrian Smith]

Thanks for the incredible amount of work you put into GWT, and for this 
release. Just tried it out, enjoyed replacing Lombok "var" with proper Java 
"var" :-)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d6687a9b-809b-4f22-8c8a-749a70f04aa7%40googlegroups.com.

Re: GWT 2.9.0 release

[Hamid Razoki]

Congratulations everyone

Le jeu. 14 mai 2020 à 11:20, Dr. Lofi Dewanto  a
écrit :

> Congrats to the team!!! Great news!
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/e911522f-2bb9-4d6a-a592-5b7d8ce86409%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACgjETYAhn3mpdtpzefmyzq93oS83cwbnX37Wo79XfUpg5S6rw%40mail.gmail.com.

Re: [ANN] JRS gwt-time 1.4.8 release

[foal]

It is also the way, but with HUGE drawback for me -  I can't work with 
SNAPSHOT, and there is no schedule for GWT releases. I hope with a new 
release it will change.

Stas.

 

On Thursday, May 14, 2020 at 9:33:25 AM UTC+2, Jens wrote:
>
>
> Is there any way to correctly extend/replace core GWT emulation?
>>
>
> You have to contribute it to GWT SDK so there is only a single emulation 
> for everyone of that Java SDK class. As soon as you replace a GWT SDK 
> emulation things can break badly.
>
> -- J.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/dad00673-2906-4c4d-89dd-317ed6b14aed%40googlegroups.com.

Re: [ANN] JRS gwt-time 1.4.8 release

[foal]

Hmm,

But the main issue that I have how to *create the Locale* object to pass it 
into the methods. The rest is possible to solve somehow.

Stas 

On Thursday, May 14, 2020 at 11:58:48 AM UTC+2, Thomas Broyer wrote:
>
>
>
> On Thursday, May 14, 2020 at 7:30:11 AM UTC+2, foal wrote:
>>
>> Hi,
>>
>> Yes, I have and not happy with it. Can I ask how to emulate some Java 
>> methods that required Locale as a parameter? The GWT version is not enough. 
>> My version can cause problems. At least I need to describe it correctly on 
>> the project page.
>>
>
> I don't mean introducing a new kind of Locale.
> For example, you've added toLanguageTag as an instance method, and 
> getAvailableLocales as a static method.
> Then do:
> public class LocaleExt {
>   public static String toLanguageTag(Locale locale) { … }
>   public static Locale[] getAvailableLocales() { … }
> }
>
> (and for performance, maybe cache the computed language tag in a 
> java.util.Map or a JS WeakMap 
> 
> )
> and everywhere in your code where you used to call locale.toLanguageTag() 
> or Locale.getAvailableLocales() then replace them with 
> LocaleExt.toLanguageTag(locale) or LocaleExt.getAvailableLocales() 
> respectively.
>
> Then the 
> SimpleDateTimeFormatStyleProvider#getFormatter(FormatStyle,FormatStyle,Chronology,Locale)
>  
> emulation can keep the exact same signature.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/892a0a60-aa05-4e8a-af3d-978d8b3d2e40%40googlegroups.com.

Re: GWT 2.9.0 release

[Dr. Lofi Dewanto]

Congrats to the team!!! Great news!

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e911522f-2bb9-4d6a-a592-5b7d8ce86409%40googlegroups.com.

Re: determine what table rows and columns are *actually* visible? (for scrollIntoView purposes.)

[Thomas Broyer]

You can get the actual  element using getRowElement() and compute 
everything from there, based on the element's offsetParent, offsetTop and 
offsetLeft.

BTW, depending on the browsers you need to support, you might be able to 
"just" use scrollIntoView with an options dictionary to center the cell: 
https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView

On Wednesday, May 13, 2020 at 11:49:34 PM UTC+2, Linus Kamb wrote:
>
> I have a DataGrid with a pager with a page size of 50 inside a 
> ScrollPanel.  When I ask the grid for the visible range, it give me a range 
> of 50 rows, the size of the page.   But what I can actually see at any 
> given time inside the ScrollPanel is often considerably fewer rows than the 
> page size.
>
> Is there any way to determine what rows and columns are *actually* visible 
> in the viewport of the ScrollPanel?
>
> The driver behind this is that I want to be able to programmatically 
> scroll a row+cell in to view, but I would like to scroll so the row+cell is 
> more or less in the center of the view, instead of just scrolled in to view 
> at the edge.  What I've tried to do is pick a row / column that is either 
> farther down / right or up / left so scroll in to view, but those 
> corrections depend on what is currently visible.
>
> Perhaps there is a "correct" way to do this.
>
> Thanks in advance.
> - Linus
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1708b179-1b4e-4ee0-818b-a3448bf8c814%40googlegroups.com.

Re: GWT 2.9.0 release

[Vassilis Virvilis]

Congrats to everybody involved.

On Thu, May 14, 2020 at 11:59 AM Filipe Sousa  wrote:

> Wonderful news.
>
> Thank you for the work and the commitment with this release.
>
> On Thursday, May 14, 2020 at 4:40:25 AM UTC+1, Colin Alworth wrote:
>>
>> Today we are pleased to announce the next release of GWT, version 2.9.0.
>> Some highlights of this release:
>>  * GWT supports Java 9, 10, 11 language features.
>>  * The elemental2 1.0.0 release is supported, along with
>> jsinterop-annotations 2.0.0 (except @JsAsync, which requires dropping
>> support for older browsers, and @JsEnum, which assumes closure-compiler
>> semantics, so isn't appropriate for GWT2), bringing GWT2 in line with J2CL.
>> Since this is now an official stable release of elemental2, the JSNI-based
>> elemental that is included with GWT is deprecated, and will be removed in a
>> future release.
>>  * The release was tested on a variety of operating systems, on Java 8,
>> 11, and 14. Java 7 is no longer officially supported, and future builds
>> will be compiled for Java 8 as the minimum required version.
>>
>>
>> Starting shortly after this release, we're going to be changing the
>> release process slightly - there will be more frequent dated releases
>> (something like 2.9-20200701) that occur every few months, and minor/bug
>> fix releases that happen intermittently to signify that a more lengthy
>> manual testing and acceptance process has taken place. The idea is that
>> with more frequent releases, changes will make their way faster to the
>> developers that want them, while for others, more heavily tested releases
>> for maintenance-mode projects will still be available.
>>
>> We'll also be talking soon on the contributors list about the upcoming
>> releases of individual projects that represent the various modules found in
>> gwt-user.jar, updated and tested for use in either GWT2 or J2CL.
>>
>> We're experiencing some issues in updating the gwtproject.org website,
>> but to get this release out while that is managed, find the zip download
>> and the release notes below. Maven/Gradle/Ivy users, just update the GWT
>> SDK versions to 2.9.0 - the various plugins will be updated as needed in
>> the coming days.
>>
>> GWT SDK zip download:
>> https://storage.googleapis.com/gwt-releases/gwt-2.9.0.zip
>>
>> 
>>
>> Release Notes for 2.9.0:
>>
>> Highlights
>>
>>- Able to compile projects with jsinterop-base 1.0.0, elemental2
>>1.0.0, and jsinterop-annotations 2.0.0. With the exception of @JsAsync and
>>@JsEnum, this brings GWT2 to be compatible across these tools with J2CL.
>>- Added support for Java language levels 9, 10, and 11.
>>- Officially, support is dropped for running the GWT compiler or
>>server-side tooling on Java 7. The GWT distribution is still compiled to
>>run on Java 7 for this release, but no guarantees are made about whether 
>> or
>>not this will work. Future versions will compile bytecode for Java 8+. The
>>release was tested and found to work cross platform when run with Java 8,
>>11, and 14.
>>
>>
>> Deprecations
>>
>>- Elemental has been officially deprecated - it is still included in
>>this release, but may not appear in future releases. Instead, we encourage
>>the use of the Elemental2 libraries, which are compatible with both GWT2
>>and J2CL.
>>- Removed NoSuchMethodException emulation.
>>
>>
>> Bug fixes
>>
>>- Fixes Arrays.binarySearch semantics for float[] and double[]
>>- Adds Support multi-line messages in errors/exceptions
>>- Adds shutdown hook in DiskCache to clean up temp files
>>- Cache Gecko version to lower CPU usage on FireFox
>>- Do not assume that "this" is always non null.
>>- Updates globals for Firefox version 60.0.2, Chrome 66.0.3359.45
>>- Fixes String.regionMatches.
>>- Native JsMethods allowed to coexist with implementations with the
>>same name.
>>- Make sure lambdas box, unbox and insert erasure casts when
>>necessary.
>>- Negative zero treated properly in Double/Float.compare()
>>
>>
>> Miscellaneous
>>
>>- Updates CLDR to version 34.
>>- Arrays now implement Cloneable
>>- Link backing errors together with a cause attribute, start tracking
>>suppressed errors in addition to the cause in underlying error object.
>>- Add AtomicReference to gwt/emul.
>>- Propagate script nonces via ScriptInjector
>>- Add partial emulation for ExecutorService and
>>ScheduledExecutorService
>>- Emulate java.util.concurrent.Flow
>>- Emulate javax.annotation{,.processing}.Generated
>>- Make sure "goog.global" is $wnd if not defined.
>>- Add when-linker-added element definition
>>- Add Reader and StringReader emulation.
>>- Remove GWT version check.
>>- Do not show "unusable-by-js" warning for synthetic methods.
>>- Update unmodifiableList to throw on Java8 methods.
>>- Disable DataflowOptimizer by default and emit a warning when used
>

Re: [ANN] JRS gwt-time 1.4.8 release

[Thomas Broyer]

On Thursday, May 14, 2020 at 7:30:11 AM UTC+2, foal wrote:
>
> Hi,
>
> Yes, I have and not happy with it. Can I ask how to emulate some Java 
> methods that required Locale as a parameter? The GWT version is not enough. 
> My version can cause problems. At least I need to describe it correctly on 
> the project page.
>

I don't mean introducing a new kind of Locale.
For example, you've added toLanguageTag as an instance method, and 
getAvailableLocales as a static method.
Then do:
public class LocaleExt {
  public static String toLanguageTag(Locale locale) { … }
  public static Locale[] getAvailableLocales() { … }
}

(and for performance, maybe cache the computed language tag in a 
java.util.Map or a JS WeakMap 

)
and everywhere in your code where you used to call locale.toLanguageTag() 
or Locale.getAvailableLocales() then replace them with 
LocaleExt.toLanguageTag(locale) or LocaleExt.getAvailableLocales() 
respectively.

Then the 
SimpleDateTimeFormatStyleProvider#getFormatter(FormatStyle,FormatStyle,Chronology,Locale)
 
emulation can keep the exact same signature.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/b14fdf84-f8e9-45fc-baf9-bc85ada2a796%40googlegroups.com.

Re: GWT 2.9.0 release

[Filipe Sousa]

Wonderful news.

Thank you for the work and the commitment with this release.

On Thursday, May 14, 2020 at 4:40:25 AM UTC+1, Colin Alworth wrote:
>
> Today we are pleased to announce the next release of GWT, version 2.9.0. 
> Some highlights of this release:
>  * GWT supports Java 9, 10, 11 language features.
>  * The elemental2 1.0.0 release is supported, along with 
> jsinterop-annotations 2.0.0 (except @JsAsync, which requires dropping 
> support for older browsers, and @JsEnum, which assumes closure-compiler 
> semantics, so isn't appropriate for GWT2), bringing GWT2 in line with J2CL. 
> Since this is now an official stable release of elemental2, the JSNI-based 
> elemental that is included with GWT is deprecated, and will be removed in a 
> future release.
>  * The release was tested on a variety of operating systems, on Java 8, 
> 11, and 14. Java 7 is no longer officially supported, and future builds 
> will be compiled for Java 8 as the minimum required version.
>
>
> Starting shortly after this release, we're going to be changing the 
> release process slightly - there will be more frequent dated releases 
> (something like 2.9-20200701) that occur every few months, and minor/bug 
> fix releases that happen intermittently to signify that a more lengthy 
> manual testing and acceptance process has taken place. The idea is that 
> with more frequent releases, changes will make their way faster to the 
> developers that want them, while for others, more heavily tested releases 
> for maintenance-mode projects will still be available.
>
> We'll also be talking soon on the contributors list about the upcoming 
> releases of individual projects that represent the various modules found in 
> gwt-user.jar, updated and tested for use in either GWT2 or J2CL.
>
> We're experiencing some issues in updating the gwtproject.org website, 
> but to get this release out while that is managed, find the zip download 
> and the release notes below. Maven/Gradle/Ivy users, just update the GWT 
> SDK versions to 2.9.0 - the various plugins will be updated as needed in 
> the coming days.
>
> GWT SDK zip download: 
> https://storage.googleapis.com/gwt-releases/gwt-2.9.0.zip
>
> 
>
> Release Notes for 2.9.0:
>
> Highlights
>
>- Able to compile projects with jsinterop-base 1.0.0, elemental2 
>1.0.0, and jsinterop-annotations 2.0.0. With the exception of @JsAsync and 
>@JsEnum, this brings GWT2 to be compatible across these tools with J2CL.
>- Added support for Java language levels 9, 10, and 11.
>- Officially, support is dropped for running the GWT compiler or 
>server-side tooling on Java 7. The GWT distribution is still compiled to 
>run on Java 7 for this release, but no guarantees are made about whether 
> or 
>not this will work. Future versions will compile bytecode for Java 8+. The 
>release was tested and found to work cross platform when run with Java 8, 
>11, and 14.
>
>
> Deprecations
>
>- Elemental has been officially deprecated - it is still included in 
>this release, but may not appear in future releases. Instead, we encourage 
>the use of the Elemental2 libraries, which are compatible with both GWT2 
>and J2CL.
>- Removed NoSuchMethodException emulation.
>
>
> Bug fixes
>
>- Fixes Arrays.binarySearch semantics for float[] and double[]
>- Adds Support multi-line messages in errors/exceptions
>- Adds shutdown hook in DiskCache to clean up temp files
>- Cache Gecko version to lower CPU usage on FireFox
>- Do not assume that "this" is always non null.
>- Updates globals for Firefox version 60.0.2, Chrome 66.0.3359.45
>- Fixes String.regionMatches.
>- Native JsMethods allowed to coexist with implementations with the 
>same name.
>- Make sure lambdas box, unbox and insert erasure casts when necessary.
>- Negative zero treated properly in Double/Float.compare()
>
>
> Miscellaneous
>
>- Updates CLDR to version 34.
>- Arrays now implement Cloneable
>- Link backing errors together with a cause attribute, start tracking 
>suppressed errors in addition to the cause in underlying error object.
>- Add AtomicReference to gwt/emul.
>- Propagate script nonces via ScriptInjector
>- Add partial emulation for ExecutorService and 
>ScheduledExecutorService
>- Emulate java.util.concurrent.Flow
>- Emulate javax.annotation{,.processing}.Generated
>- Make sure "goog.global" is $wnd if not defined.
>- Add when-linker-added element definition
>- Add Reader and StringReader emulation.
>- Remove GWT version check.
>- Do not show "unusable-by-js" warning for synthetic methods.
>- Update unmodifiableList to throw on Java8 methods.
>- Disable DataflowOptimizer by default and emit a warning when used
>
> For more detail, see the commit log 
> .
>
>
> 
>
> Finally, if you haven't already done so, please

Re: [ANN] JRS gwt-time 1.4.8 release

[Jens]

> Is there any way to correctly extend/replace core GWT emulation?
>

You have to contribute it to GWT SDK so there is only a single emulation 
for everyone of that Java SDK class. As soon as you replace a GWT SDK 
emulation things can break badly.

-- J.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/24dd52f8-af9c-491f-8fdf-ba121dc3ac6e%40googlegroups.com.