Re: GWT 2.10.0 release

2022-06-24 Thread Craig Mitchell
Fantastic work!  Installed it, and everything worked first go.  Well done 
all, and thank you!

-- 
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/9535458b-f1a9-4850-9681-3eaacd7d4f7en%40googlegroups.com.


Re: Install GWT plugin for Firefox26

2022-06-24 Thread hprc
Older development modes should not be used.
This required a plugin on the browser side.
What's more, this plugin existed for each browser version.
In other words, since the current browser is updated frequently, "plug-ins 
corresponding to each version" are always required.

But rest assured.
[super dev mode] does not require a browser plugin.
Therefore, we can respond immediately to IE, chorme, FF.

Therefore, please use super dev mode.
No installation required

2022年6月25日土曜日 3:46:03 UTC+9 dis0...@gmail.com:

> Thank you for an answer!
> I have to maintain the application that is old enough to be left w/o any 
> developer that created it. Our organization Confluence page is my only 
> reference now. And I follow it as close as I can. It worked, including the 
> local run mode. Till this year.
> I can hardly imagine how should I change the procedure. So, the fact that 
> *nobody 
> nowadays still uses the "legacy devmode" with browser plugins* has at 
> least one exception: I do use it.
> Can you please help me to install the plugin?
> Thanks!
>
> On Friday, June 24, 2022 at 5:55:26 PM UTC+3 t.br...@gmail.com wrote:
>
>> Is your app that old that you cannot use SuperDevMode ? It exists since 
>> GWT 2.5 which will soon be 10 years old ‼ with the first "really usable" 
>> version in GWT 2.7, nearly 8 years ago.
>> https://www.gwtproject.org/articles/superdevmode.html
>> Nobody nowadays still uses the "legacy devmode" with browser plugins.
>>
>> On Friday, June 24, 2022 at 11:29:44 AM UTC+2 dis0...@gmail.com wrote:
>>
>>> I maintain the (old) application with the GWT part. To run the system 
>>> locally (bugs fixing or minor code changes) I need the FF26 - and the GWT 
>>> plugin.
>>> Each time I have to setup my machine for the task, I install the FF26 
>>> and the GWT plugin. No problems in the past. But this year I get the error 
>>> while doing it:
>>>
>>> Secure Connection Failed
>>> An error occurred during a connection to www.gwtproject.org. Cannot 
>>> communicate securely with peer: no common encryption algorithm(s). (Error 
>>> code: ssl_error_no_cypher_overlap) 
>>>
>>> How can I install the GWT plugin on my FF26 browser?
>>>
>>> Thanks!
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2d9c8e73-8c13-40be-8515-af6bd996006en%40googlegroups.com.


Re: Install GWT plugin for Firefox26

2022-06-24 Thread d is
Thank you for an answer!
I have to maintain the application that is old enough to be left w/o any 
developer that created it. Our organization Confluence page is my only 
reference now. And I follow it as close as I can. It worked, including the 
local run mode. Till this year.
I can hardly imagine how should I change the procedure. So, the fact that 
*nobody 
nowadays still uses the "legacy devmode" with browser plugins* has at least 
one exception: I do use it.
Can you please help me to install the plugin?
Thanks!

On Friday, June 24, 2022 at 5:55:26 PM UTC+3 t.br...@gmail.com wrote:

> Is your app that old that you cannot use SuperDevMode ? It exists since 
> GWT 2.5 which will soon be 10 years old ‼ with the first "really usable" 
> version in GWT 2.7, nearly 8 years ago.
> https://www.gwtproject.org/articles/superdevmode.html
> Nobody nowadays still uses the "legacy devmode" with browser plugins.
>
> On Friday, June 24, 2022 at 11:29:44 AM UTC+2 dis0...@gmail.com wrote:
>
>> I maintain the (old) application with the GWT part. To run the system 
>> locally (bugs fixing or minor code changes) I need the FF26 - and the GWT 
>> plugin.
>> Each time I have to setup my machine for the task, I install the FF26 and 
>> the GWT plugin. No problems in the past. But this year I get the error 
>> while doing it:
>>
>> Secure Connection Failed
>> An error occurred during a connection to www.gwtproject.org. Cannot 
>> communicate securely with peer: no common encryption algorithm(s). (Error 
>> code: ssl_error_no_cypher_overlap) 
>>
>> How can I install the GWT plugin on my FF26 browser?
>>
>> Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/4d20f3c3-b42d-4c76-b9cb-cfa481e5e5fcn%40googlegroups.com.


Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-06-24 Thread mtils...@gmail.com
Any clue about how you got it to work? It still don't work for me on 
2022-03. It installs but does not really add anything. On 2022-06 it 
refuses to install.


On Tuesday, 24 May 2022 at 09:08:45 UTC+2 eliasbala...@gmail.com wrote:

> This seems to be working finally.
>
> To my surprise, I repeated the experiment and [GWT Eclipse Plugin] is 
> fully accessible and operational.
>
> I am now confused.
>
> On Monday, 23 May 2022 at 23:37:41 UTC+1 hprc wrote:
>
>>
>> I also use the GWT Eclipse Plugin.
>> Currently, the Eclipse side is up to 202103, and seems to be up to JDK1.8.
>>
>> The official documentation still only describes this plugin, so I'd like 
>> you to add a method with the Moven plugin as soon as possible.
>> (Preferably with illustrations)
>> 2022年5月24日火曜日 6:57:01 UTC+9 eliasb...@gmail.com:
>>
>>> [GWT Eclipse Plugin] has served us very well.
>>>
>>> It is quite unfortunate but I fear the time for putting it to rest is 
>>> approaching, if it hasn't already come.
>>>
>>> I just don't want to give up yet :-)
>>>
>>> On Monday, 23 May 2022 at 03:46:42 UTC+1 hprc wrote:
>>>

 It's certainly interesting.
 However, do you recognize that the development of [GWT Eclipse Plugin] 
 will not be continued anymore?
 2022年5月22日日曜日 18:16:34 UTC+9 eliasb...@gmail.com:

> Interesting...
>
> But you are using STS distribution not the standard, perhaps something 
> is different in the STS distribution compared to the primary Eclipse 
> Foundation's distribution.
>
> On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:
>
>> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
>> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>>
>> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell wrote:
>>
>>> I'm on Eclipse 2021-09 (4.21.0) and it works fine.
>>>
>>> However, after this version, the Google plugin stops working  
>>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659 
>>>  
>>> so I haven't tried later versions.
>>>
>>> On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com 
>>> wrote:
>>>
 Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still 
 working.

 Under Eclipse 2022-03, the preferences page, the GWT Development 
 view and the run configurations are not accessible.

 This is crucial for certain teams relying on GWT Eclipse Plugin for 
 running applications from within the Eclipse IDE and locks users to 
 Eclipse 
 2021-03 permanently, unless this can be fixed.



-- 
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/df6aa266-7eaa-451f-a06e-664f72cbfba8n%40googlegroups.com.


Re: Install GWT plugin for Firefox26

2022-06-24 Thread Thomas Broyer
Is your app that old that you cannot use SuperDevMode ? It exists since GWT 
2.5 which will soon be 10 years old ‼ with the first "really usable" 
version in GWT 2.7, nearly 8 years ago.
https://www.gwtproject.org/articles/superdevmode.html
Nobody nowadays still uses the "legacy devmode" with browser plugins.

On Friday, June 24, 2022 at 11:29:44 AM UTC+2 dis0...@gmail.com wrote:

> I maintain the (old) application with the GWT part. To run the system 
> locally (bugs fixing or minor code changes) I need the FF26 - and the GWT 
> plugin.
> Each time I have to setup my machine for the task, I install the FF26 and 
> the GWT plugin. No problems in the past. But this year I get the error 
> while doing it:
>
> Secure Connection Failed
> An error occurred during a connection to www.gwtproject.org. Cannot 
> communicate securely with peer: no common encryption algorithm(s). (Error 
> code: ssl_error_no_cypher_overlap) 
>
> How can I install the GWT plugin on my FF26 browser?
>
> Thanks!
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/62571efa-5c52-48a6-a08b-fbb9b8ebec33n%40googlegroups.com.


Re: GWT 2.10.0 release

2022-06-24 Thread lofid...@gmail.com
Yay, thanks a lot to all GWT contributors! 

Frank schrieb am Freitag, 24. Juni 2022 um 08:41:22 UTC+2:

> Great !
> Thanks
>
> Op vrijdag 24 juni 2022 om 01:16:54 UTC+2 schreef hprc:
>
>> Yay!
>> Thank you Colin and everyone.
>> GWT is getting bigger and bigger.
>> 2022年6月24日金曜日 1:16:50 UTC+9 nilo...@gmail.com:
>>
>>> I'm very happy to announce the release of GWT 2.10.0. This is the first 
>>> release using our new groupId, org.gwtproject, and the final release using 
>>> com.google.gwt. If you resolve dependencies from Maven Central, please be 
>>> certain that your project is using com.google.gwt:gwt (or 
>>> org.gwtproject:gwt) as a BOM, so that you are certain to have consistent 
>>> versions of gwt-user and gwt-dev, even across groupIds.
>>>
>>> For this release, either groupId will work, but future releases will 
>>> only be made on the org.gwtproject groupId.
>>>
>>> The zip download of the GWT SDK is available at 
>>> https://github.com/gwtproject/gwt/releases/download/2.10.0/gwt-2.10.0.zip
>>>
>>> --
>>>
>>> Release notes for GWT 2.10.0, taken from 
>>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
>>>
>>> Highlights 
>>>
>>>- 
>>>
>>>Updated to HtmlUnit 2.55.0 and Jetty 9.4.44. With this newer 
>>>HtmlUnit build comes support for Promise in unit tests, and the browser 
>>>strings that can be specified when running tests are “FF”, “Chrome”, 
>>> “IE” 
>>>(for IE11), “Edge”, and “Safari”.
>>>- 
>>>
>>>Tested support for running on Java 17, dropped remaining support for 
>>>running on Java 7.
>>>- 
>>>
>>>Maven groupId is formally changed to org.gwtproject, projects should 
>>>take care to make sure they are using either the old 
>>>com.google.gwt:gwt BOM or the new org.gwtproject:gwt BOM to sure 
>>>that Maven or Gradle correctly handle this change. This will be the last 
>>>published version using the com.google.gwt groupId.
>>>- 
>>>
>>>Dropped support for IE 8, 9, and 10.
>>>
>>> Bug fixes 
>>>
>>>- Correct Long.hashCode semantics
>>>- Support CLASSPATH environment variable when creating child 
>>>processes, fixing a bug where Windows could fail with a long list of 
>>>arguments.
>>>- Use Function.name instead of displayName to support visible method 
>>>names in Chrome 93+.
>>>- Allow stack traces to be available in Chrome when loading scripts 
>>>from a remote origin.
>>>
>>> JRE Emulation 
>>>
>>>- Added OutputStreamWriter emulation.
>>>- Support StringReader mark() and reset() methods.
>>>- Added StrictMath emulation.
>>>- Added BufferedWriter emulation.
>>>- Added incomplete PrintStream emulation.
>>>- Add Charset.defaultCharset() emulation.
>>>- Improve BigInteger emulated performance.
>>>- System.nanoTime() emulation with performance.now().
>>>- Added Optional.isEmpty emulation.
>>>- JRE Emulation improvements/simplifications to facilitate J2CL’s 
>>>WASM support. Note that these do not always offer specific improvements 
>>> to 
>>>GWT itself, but helps to keep the codebases consistent.
>>>
>>> Miscellaneous 
>>>
>>>- Add support to compile GWT itself in Java 9+.
>>>- Improve compiled code size for applications that never use 
>>>streams, by avoiding referencing streams from Throwable.
>>>
>>> For more detail, see the commit log 
>>> .
>>>
>>

-- 
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/3b3465dc-cd9d-4a79-babc-338ecb1ca399n%40googlegroups.com.


Install GWT plugin for Firefox26

2022-06-24 Thread d is
I maintain the (old) application with the GWT part. To run the system 
locally (bugs fixing or minor code changes) I need the FF26 - and the GWT 
plugin.
Each time I have to setup my machine for the task, I install the FF26 and 
the GWT plugin. No problems in the past. But this year I get the error 
while doing it:

Secure Connection Failed
An error occurred during a connection to www.gwtproject.org. Cannot 
communicate securely with peer: no common encryption algorithm(s). (Error 
code: ssl_error_no_cypher_overlap) 

How can I install the GWT plugin on my FF26 browser?

Thanks!

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/acfe623f-6e21-4bbe-a488-5bad31dbca8cn%40googlegroups.com.


Re: GWT 2.10.0 release

2022-06-24 Thread Frank
Great !
Thanks

Op vrijdag 24 juni 2022 om 01:16:54 UTC+2 schreef hprc:

> Yay!
> Thank you Colin and everyone.
> GWT is getting bigger and bigger.
> 2022年6月24日金曜日 1:16:50 UTC+9 nilo...@gmail.com:
>
>> I'm very happy to announce the release of GWT 2.10.0. This is the first 
>> release using our new groupId, org.gwtproject, and the final release using 
>> com.google.gwt. If you resolve dependencies from Maven Central, please be 
>> certain that your project is using com.google.gwt:gwt (or 
>> org.gwtproject:gwt) as a BOM, so that you are certain to have consistent 
>> versions of gwt-user and gwt-dev, even across groupIds.
>>
>> For this release, either groupId will work, but future releases will only 
>> be made on the org.gwtproject groupId.
>>
>> The zip download of the GWT SDK is available at 
>> https://github.com/gwtproject/gwt/releases/download/2.10.0/gwt-2.10.0.zip
>>
>> --
>>
>> Release notes for GWT 2.10.0, taken from 
>> https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0
>>
>> Highlights 
>>
>>- 
>>
>>Updated to HtmlUnit 2.55.0 and Jetty 9.4.44. With this newer HtmlUnit 
>>build comes support for Promise in unit tests, and the browser strings 
>> that 
>>can be specified when running tests are “FF”, “Chrome”, “IE” (for IE11), 
>>“Edge”, and “Safari”.
>>- 
>>
>>Tested support for running on Java 17, dropped remaining support for 
>>running on Java 7.
>>- 
>>
>>Maven groupId is formally changed to org.gwtproject, projects should 
>>take care to make sure they are using either the old 
>>com.google.gwt:gwt BOM or the new org.gwtproject:gwt BOM to sure that 
>>Maven or Gradle correctly handle this change. This will be the last 
>>published version using the com.google.gwt groupId.
>>- 
>>
>>Dropped support for IE 8, 9, and 10.
>>
>> Bug fixes 
>>
>>- Correct Long.hashCode semantics
>>- Support CLASSPATH environment variable when creating child 
>>processes, fixing a bug where Windows could fail with a long list of 
>>arguments.
>>- Use Function.name instead of displayName to support visible method 
>>names in Chrome 93+.
>>- Allow stack traces to be available in Chrome when loading scripts 
>>from a remote origin.
>>
>> JRE Emulation 
>>
>>- Added OutputStreamWriter emulation.
>>- Support StringReader mark() and reset() methods.
>>- Added StrictMath emulation.
>>- Added BufferedWriter emulation.
>>- Added incomplete PrintStream emulation.
>>- Add Charset.defaultCharset() emulation.
>>- Improve BigInteger emulated performance.
>>- System.nanoTime() emulation with performance.now().
>>- Added Optional.isEmpty emulation.
>>- JRE Emulation improvements/simplifications to facilitate J2CL’s 
>>WASM support. Note that these do not always offer specific improvements 
>> to 
>>GWT itself, but helps to keep the codebases consistent.
>>
>> Miscellaneous 
>>
>>- Add support to compile GWT itself in Java 9+.
>>- Improve compiled code size for applications that never use streams, 
>>by avoiding referencing streams from Throwable.
>>
>> For more detail, see the commit log 
>> .
>>
>

-- 
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/c09f855c-de35-4971-9258-4152a2db1eddn%40googlegroups.com.