Re: [gwt-contrib] Re: Preparing for GWT 2.11 release

[Juan Pablo Gardella]

Thanks I will check using a snapshot then.

On Thu, Nov 23, 2023 at 1:03 PM Colin Alworth  wrote:

> We're still in the "please help us review the last few merges" phase
> (especially looking for notes on deprecating using DevMode as an app
> server, and comments on if tests added for other PRs seem sufficient), then
> we'll make some release artifacts (late next week is my guess). I'm hoping
> to merge most of the open PRs, so we want to not start testing until we've
> landed that changes that will make this release.
>
> That being said, we ship HEAD-SNAPSHOT every night off of main, you can
> add https://oss.sonatype.org/content/repositories/snapshots/ as a
> snapshot repository to your project to use that build (be certain you are
> using org.gwtproject groupids). If you need nightly download zips, they are
> available at
> https://github.com/gwtproject/gwt/actions/workflows/full-check.yml, click
> any build, scroll down artifacts, and download gwt-java17.zip. While this
> was built with Java 17, it is compatible with Java 8+ and will be used for
> the release. The other builds should be nearly identical - the main change
> should be in the javadoc output. The build produced from Java8 is
> substantially smaller since it doesn't include javadoc at all, since the
> APIs we now use are not compatible there.
>
> On Thursday, November 23, 2023 at 7:36:55 AM UTC-6 Juan Pablo Gardella
> wrote:
>
>> Hello, is gwt-2.11 artifacts available somewhere for testing against the
>> applications I am currently working on?
>>
>> On Tue, Nov 14, 2023, 11:37 PM Colin Alworth  wrote:
>>
>>> It has taken longer than we had hoped, but I think we're just about
>>> ready - GWT itself can build on Java 17 (and can run on Java 23), JRE
>>> emulation is nearly caught up to where we wanted with Java 11, and
>>> jakarta.servlet support is hopefully finished and partially tested in
>>> non-trivial apps.
>>>
>>> Here's my view of what might land before we cut a release:
>>>
>>>- The jakarta.servlet patch is now at
>>>https://github.com/gwtproject/gwt/pull/9845, and is effectively
>>>ready to land. To my knowledge, no jakarta project has tested the
>>>requestfactory-*.jars yet.
>>>- As above, we need confirmation that
>>>https://github.com/gwtproject/gwt/pull/9785 solves the problem it
>>>was created for.
>>>- As above https://github.com/gwtproject/gwt/pull/9799 (fixing some
>>>ternary expressions and other type unions) should get at least one more
>>>review, approval. This will be applicable for Java 17 language support.
>>>- Two more JRE emulation patches:
>>>https://github.com/gwtproject/gwt/pull/9860 needs a review, and
>>>https://github.com/gwtproject/gwt/pull/9862 needs follow-up and
>>>another review.
>>>
>>> If this is the last release that can run the compiler and dev mode on
>>> Java 8, we will want to update Jetty in the next release as well. That
>>> might suggest one more change, deprecating the use of "-server" in DevMode.
>>> Please see https://github.com/gwtproject/gwt/issues/9863 for more
>>> details. In the coming days I'll put together a patch for this.
>>>
>>> After we've merged or deferred these PRs, the next step will be asking
>>> for testing volunteers and cutting an RC release. I'm hoping we can begin
>>> that process within two weeks - if you're interested in helping us test
>>> this release, please reply to this message or directly with the
>>> OS/JVM/Browsers you have at your disposal, and I'll make sure you are
>>> included. As usual, the testing process will probably take a week or so to
>>> get the desired coverage, and then we'll formally release GWT 2.11.0.
>>>
>>> On Tuesday, May 23, 2023 at 3:11:51 PM UTC-5 Rocco De Angelis wrote:
>>>
>>>> Hi Colin,
>>>>
>>>> if you need some help, I'm feeling to help.
>>>> Specially the jakarta stuff is important for us.
>>>> Do you find the time to have a look to the open PR?
>>>>
>>>> BR
>>>> Rocco
>>>>
>>>> Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2:
>>>>
>>>>> There have been a few suggestions of making a release in the near
>>>>> future, and it seemed like it might be a good idea to summarize pending
>>>>> development, ask for help to land these, and see if anything else needs to
>>>>> be addressed before shipping.
>>&g

Re: [gwt-contrib] Re: Preparing for GWT 2.11 release

[Juan Pablo Gardella]

Hello, is gwt-2.11 artifacts available somewhere for testing against the
applications I am currently working on?

On Tue, Nov 14, 2023, 11:37 PM Colin Alworth  wrote:

> It has taken longer than we had hoped, but I think we're just about ready
> - GWT itself can build on Java 17 (and can run on Java 23), JRE emulation
> is nearly caught up to where we wanted with Java 11, and jakarta.servlet
> support is hopefully finished and partially tested in non-trivial apps.
>
> Here's my view of what might land before we cut a release:
>
>- The jakarta.servlet patch is now at
>https://github.com/gwtproject/gwt/pull/9845, and is effectively ready
>to land. To my knowledge, no jakarta project has tested the
>requestfactory-*.jars yet.
>- As above, we need confirmation that
>https://github.com/gwtproject/gwt/pull/9785 solves the problem it was
>created for.
>- As above https://github.com/gwtproject/gwt/pull/9799 (fixing some
>ternary expressions and other type unions) should get at least one more
>review, approval. This will be applicable for Java 17 language support.
>- Two more JRE emulation patches:
>https://github.com/gwtproject/gwt/pull/9860 needs a review, and
>https://github.com/gwtproject/gwt/pull/9862 needs follow-up and
>another review.
>
> If this is the last release that can run the compiler and dev mode on Java
> 8, we will want to update Jetty in the next release as well. That might
> suggest one more change, deprecating the use of "-server" in DevMode.
> Please see https://github.com/gwtproject/gwt/issues/9863 for more
> details. In the coming days I'll put together a patch for this.
>
> After we've merged or deferred these PRs, the next step will be asking for
> testing volunteers and cutting an RC release. I'm hoping we can begin that
> process within two weeks - if you're interested in helping us test this
> release, please reply to this message or directly with the OS/JVM/Browsers
> you have at your disposal, and I'll make sure you are included. As usual,
> the testing process will probably take a week or so to get the desired
> coverage, and then we'll formally release GWT 2.11.0.
>
> On Tuesday, May 23, 2023 at 3:11:51 PM UTC-5 Rocco De Angelis wrote:
>
>> Hi Colin,
>>
>> if you need some help, I'm feeling to help.
>> Specially the jakarta stuff is important for us.
>> Do you find the time to have a look to the open PR?
>>
>> BR
>> Rocco
>>
>> Colin Alworth schrieb am Mittwoch, 17. Mai 2023 um 16:44:58 UTC+2:
>>
>>> There have been a few suggestions of making a release in the near
>>> future, and it seemed like it might be a good idea to summarize pending
>>> development, ask for help to land these, and see if anything else needs to
>>> be addressed before shipping.
>>>
>>>
>>>- There is a pending branch (not yet a PR for GWT itself) working on
>>>adding a new gwt-servlet-jakarta.jar and 
>>> requestfactory-server-jakarta.jar
>>>as part of https://github.com/gwtproject/gwt/issues/9727. There is
>>>no plan at this time to update the DevMode server to Jakarta, though that
>>>will eventually be inevitable if we move to a newer version of Jetty. 
>>> Work
>>>on this can be found at https://github.com/niloc132/gwt/pull/3.
>>>- There is a pending fix for eliminating a false positive from using
>>>some internals of protobuf to deobfuscate client side exceptions
>>>https://github.com/gwtproject/gwt/pull/9785. This is probably safe
>>>to land without more testing, but none of the reporters of this bug have
>>>verified the fix.
>>>- There's a pending fix for a bug in type unions, which can be
>>>caused by some ternary expressions and var type declarations
>>>https://github.com/gwtproject/gwt/pull/9799. A review found a few
>>>oversights in testing, and I'd appreciate another look.
>>>- There's a pending fix for a bug where debugging in firefox when
>>>assertions are enabled (for example in SDM). It turns out the bug can
>>>happen in other cases too in more subtle ways. A draft fix it at
>>>https://github.com/gwtproject/gwt/pull/9800.
>>>- GWT itself can now be built on Java 11, but not yet 17. There are
>>>a few changes pending that will permit this. Additionally, this will 
>>> enable
>>>adding more Java 9-11 JRE emulation, see the list at
>>>https://github.com/gwtproject/gwt/issues/9547.
>>>
>>>
>>> Finally, we have an open question about future Java 8 support. Beyond
>>> this release, we likely will no longer support running the compiler in Java
>>> 8, which will enable adding support for Java 12-17 language features. We
>>> can likely still build jars that will run on a Java 8 server, but just
>>> can't compile newer JS. To that end, this 2.11 release branch may be
>>> longer-lived than usual, depending on feedback and support to continue
>>> bugfix releases after 2.12 eventually ships.
>>>
>>> Are there other changes that 2.11 should included, or other
>>> 

Re: [gwt-contrib] Re: Testing for GWT 2.10.0 release

[Juan Pablo Gardella]

Thanks Colin!

On Wed, Jun 22, 2022 at 5:11 PM Colin Alworth  wrote:

> The last step of the release process is under way, Google's 2.10.0 release
> is underway, we're just waiting for the release to be performed and
> synchronized to Maven Central. When that has finished we can formally
> announce the release.
>
> I've created an issue for next steps to finish our transition to GitHub at
> https://github.com/gwtproject/gwt/issues/9756 and will follow up with a
> few proposed pull requests to make these changes.
>
> Thanks for everyone's support and patience with this process!
>
> On Sunday, May 22, 2022 at 11:00:14 AM UTC-5 mcmi...@gmail.com wrote:
>
>> Hi,
>> I could test on Windows 10 (and maybe Windows 11)
>> Browser :
>> - Firefox
>> - Edge (but Chromium only)
>> - IE 11 (End of Support on June 15th)
>> - Chrome
>>
>> JVM:
>> - 11
>> - 17
>> - 18
>> - 19 eap
>> Boris Brudnoy schrieb am Freitag, 20. Mai 2022 um 14:33:02 UTC+2:
>>
>>> I'll test. I'm on macOS Monterey 12.3.1. Can do whichever JVMs /
>>> browsers run on macOS, which AFAICT is everything but IE11.
>>>
>>> On Thursday, May 19, 2022 at 11:34:31 PM UTC-4 nilo...@gmail.com wrote:
>>>
 Hello all,

 All of the preliminary testing that I'm aware of for the upcoming
 release is complete, leaving us with a decent level of confidence in the
 changes. We have a document that outlines the release plan (with a link to
 the standard release steps and the testing process) that has undergone a
 few small tweaks, and I think is ready to go:

 https://docs.google.com/document/d/10Cn0Z7SDv0ZW5OVZdoIdw5EAEDUbtK6vracOOnxj7po/edit

 I'm now asking for volunteers who are able to test the final release
 once it is ready to go. We're hoping for a cross section of testing that
 verifies

- JVM Version: 8, 11, 17/18
- OS: Linux, OS X, Windows 8.1, 10, 11
- Browser: Chrome, Firefox, Safari, IE11, Edge (blink)

 Windows 8.1 and 10 VMs are available at
 https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/, I'm
 not presently aware of a source for Windows 11 VMs, so ideally we have a
 few people running that natively.

 Please reply to this or contact me off-list (co...@colinalworth.com)
 with the combinations you have access to and are able to test, and we'll
 organize in the next few days, and start the next steps.

 Thanks!

>>> --
> 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/5df0ff8b-6d48-4c44-a814-3e27cb98427dn%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFseDOCx7tbdqQb2LUu0RYu3b6k-HstCUAOXvewxTv5L6KA%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

After removing an old plexus-utils as suggested at #152
, I was able to
compile and run the application without issues so far. Great work!

On Mon, Apr 25, 2022 at 2:25 PM Freddy Boucher 
wrote:

> 2.10.0-new-groupid-3 works like a charm (in addition of
> net.ltgt.gwt.maven/gwt-maven-plugin 1.0.1)
> Thanks
>
> Le dimanche 24 avril 2022 à 21:34:23 UTC+2, juan_pablo_gardella a écrit :
>
>> Tried with Maven 3.8.5 and still fails with same issue. Reported at
>> https://github.com/tbroyer/gwt-maven-plugin/issues/152
>>
>> On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth  wrote:
>>
>>> I've pushed a new build with version 2.10.0-new-groupid-3 that has
>>> several @SuppressWarnings("deprecation")s added, and hopefully will solve
>>> the WARN logging issue.
>>>
>>> --
>>>
>> 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-co...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/28cff012-2206-48a8-8882-11b0ea945046n%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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/051780f4-fa98-45c2-ad36-1ebb40a38f7an%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFsengmip-YpVegW-6CP1TOeVQTnnS5OU-D%2B26c4ru1G2gQ%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

Tried with Maven 3.8.5 and still fails with same issue. Reported at
https://github.com/tbroyer/gwt-maven-plugin/issues/152

On Sun, Apr 24, 2022 at 3:59 PM Colin Alworth  wrote:

> I've pushed a new build with version 2.10.0-new-groupid-3 that has several
> @SuppressWarnings("deprecation")s added, and hopefully will solve the WARN
> logging issue.
>
> --
> 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/28cff012-2206-48a8-8882-11b0ea945046n%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFsdpiEDJOdjMYg52WnmDi-zt%3DPipSk9LXb_T-Ben9A5QYQ%40mail.gmail.com.

Re: [gwt-contrib] Preliminary testing for GWT 2.10 release

[Juan Pablo Gardella]

I tested and I updated from net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0 to
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1 in order to see the proper error (*
Value 'ie10' in not a valid value for property 'user.agent'*) instead of
[1]. After that I see following error:

[ERROR] Failed to execute goal
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app (default-package-app)
on project xxx-client: Execution default-package-app of goal
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app failed: An API
incompatibility was encountered while executing
net.ltgt.gwt.maven:gwt-maven-plugin:1.0.1:package-app:
java.lang.NoSuchMethodError:
org.codehaus.plexus.util.DirectoryScanner.setFilenameComparator(Ljava/util/Comparator;)V

Using either java8 or java11 as default java but java8 with toolchains
 for the
project. Reverted to net.ltgt.gwt.maven:gwt-maven-plugin:1.0.0 I still see
NPE[1]. No luck from my side to switch. Any ideas? I am using Apache Maven
3.6.3.

Juan

[1]
Caused by: java.lang.NullPointerException
at
net.ltgt.gwt.maven.GenerateModuleMojo.generateInheritsFromDependencies
(GenerateModuleMojo.java:251)
at net.ltgt.gwt.maven.GenerateModuleMojo.execute
(GenerateModuleMojo.java:180)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)

On Fri, Apr 22, 2022 at 3:35 PM Colin Alworth  wrote:

> I could revert the deprecations (though they were specifically added at
> your request ;) ).
>
> That said, those changed when the old IE versions were removed, and I
> didn't see the showcase start to emit those errors then. Even with the JDT
> upgrade, I still don't see them for the showcase:
>
> https://github.com/niloc132/gwt/runs/6124099314?check_suite_focus=true#step:5:3295
>
> The error also does not appear to happen when running from ant, at least
> not in the showcase sample.
>
> At a glance I can't see anything explicitly disabling deprecation warnings
> in that code. The warning is coming from JsniReferenceResolver. The linked
> log above is emitting warnings, but clearly not one for the code you see,
> even though the showcase references those types. Showcase's CwRichText
> explicitly uses the RichText widget.
>
> However, both maven and gradle projects do correctly include the warnings,
> if you happen to include those gwt modules in your project. That does make
> the iteration time a bit longer to test, but it appears we can suppress the
> warnings on a per-usage basis. I'll propose a patch (and upload a new build
> to test) as soon as I'm able.
>
>
> On Friday, April 22, 2022 at 9:12:58 AM UTC-5 Thomas Broyer wrote:
>
>> I tried changing only the version (from com.google.gwt:gwt:2.8.2 to
>> com.google.gwt:2.10.0-new-groupid-2).
>> Looking at a dependency graph (./gradlew dependencies), I can see the
>> com.google.gwt dependencies properly "relocated" to their org.gwtproject
>> equivalent 
>> Java compilation passes without warning or error, same for JVM tests (I
>> don't have much that use GWT though), and even GWT tests!  (I only have a
>> couple of them though)
>> GWT compilation emits a few unexpected warnings though:
>>[WARN] Warnings in

Re: [gwt-contrib] gwtproject.org migration, https support

[Juan Pablo Gardella]

Thanks Colin! Great work

On Mon, Mar 28, 2022 at 12:37 PM Colin Alworth  wrote:

> We've successfully migrated the gwtproject.org website to a new domain
> name server and new hosting, at Google's request. There are a few small
> differences from the old hosting:
>
>
>- HTTPS is now supported and enabled, though not yet mandatory, to
>allow a period of migration, and making sure that no downstream tools will
>break as a result of these changes. HSTS is also disabled for now. I
>propose that mid-week I will update this to always redirect to HTTPS, and
>then in another two or three weeks consider enabling HSTS if there have
>been no reported issues.
>- The samples.gwtproject.org domain now redirects to the showcase,
>rather than giving a confusing 500 error. The samples are still at this
>time hosted as static content rather than servlets.
>- The GWT application that enhances the documentation has been
>updated, picking up changes published ~2 years ago.
>- Deep links that omit "www." (for example
>gwtproject.org/doc/latest/DevGuide.html) will now redirect to the
>expected page (in this case www.gwtproject.org/doc/latest/DevGuide.html)
>rather than redirecting only to www.gwtproject.org.
>
>
> Building and deployment of the new site is currently described at
> https://github.com/Vertispan/gwtproject.org, and should be hostable with
> or without DNS entries or HTTPS (though handling your own dns for "
> gwtproject.org" itself may eventually conflict with HSTS). The README
> contains some basic details on how the hosting is structured and how to run
> on any arbitrary server. There is also a TODO list at
> https://github.com/Vertispan/gwtproject.org/blob/main/TODO.md, which
> could eventually be migrated to actual github issues.
>
> This could have been implemented through a similar build process that then
> pushed to github-pages, but at least for now we decided against this. Once
> some kind of continuous integration is in place to create pre-built
> artifacts for gwt-site-webapp and gwt-site itself, it might make sense to
> reconsider this, but for samples it still may make sense to use custom
> hosting to phase out the current static-only samples and provide some
> samples which can interact in some way with the server.
>
> If there are no objections to the current layout, configuration,
> deployment, and documentation, I propose migrating this project to
> github.com/gwtproject, as well as following up on the bullet points of
> the TODO list.
>
> --
> 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/94a1c877-78ac-40ea-9084-405514b8b3d4n%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFsf5SR%2BvhiEPWUJK8vWiwPfSPfuOUxAXnTzX0MBqp0eWXQ%40mail.gmail.com.

Re: [gwt-contrib] Re: GWT 2.10 release?

[Juan Pablo Gardella]

@co...@colinalworth.com   do yo know any ETA on
this?

On Tue, Oct 12, 2021, 5:28 AM Rocco De Angelis 
wrote:

>
> Nice +1
> chani...@gmail.com schrieb am Dienstag, 5. Oktober 2021 um 16:38:08 UTC+2:
>
>> Thank a millon, looks great ! +1
>>
>> On Friday, October 1, 2021 at 2:55:21 p.m. UTC-4 krypto...@gmail.com
>> wrote:
>>
>>> awesome +1
>>>
>>> On Fri, Oct 1, 2021 at 2:31 PM mcmi...@gmail.com 
>>> wrote:
>>>
 Sound greats +1


 nilo...@gmail.com schrieb am Donnerstag, 30. September 2021 um
 21:22:13 UTC+2:

> We've got a few changes that have been brewing or waiting to be made
> available, and it sounds like it is about time to collectively push to 
> make
> these things happen. Given the nature of some of these, I am suggesting
> that they not be folded into a bugfix release, but instead that the next
> release be 2.10.0.
>
>
> Changing Maven Central groupId
> One of the big ones is work to migrate off of the "com.google.gwt"
> groupId (note that we are not adjusting packages) and into our own
> namespace in maven, "org.gwtproject.gwt". Google's efforts to open 
> sourcing
> and encourage GWT has been very accommodating for the community, and this
> change is long past due, so that releases of GWT do not need someone with
> access to the com.google groupId in Maven Central to perform the release
> process for us. If successful, this will be the final release which uses
> the old groupId.
>
> To that end, Thomas Broyer has done a lot of work to make sure this
> path will be as smooth as possible. That work can be seen discussed
> in the mailing list
> 
> and in a github repo he wrote
>  to demonstrate
> approaches and their relative merits. No final summary was officially
> posted, but from discussions in gitter chat
> , the
> cleanest proposed option is to follow Experiment #3 for today, and
> optionally later to roll out the last two options to more easily 
> facilitate
> updates from older releases.
>
> This means that the next release will be performed first on
> org.gwtproject, and then later we will request that someone at Google
> perform the final com.google.gwt release, consisting only of pom files 
> that
> indicate relocation to the new groupId. Applications and dependencies will
> need to switch to this new groupId over time, but in theory at least, 
> using
> the researched relocation mechanism should make that fairly painless.
>
> Finally, I suggest that any release candidate that goes out only exist
> on org.gwtproject, to avoid needing to iterate with com.google releases, 
> in
> case we end up needing more than one RC in the release process.
>
> --
>
> Chrome debugging bugs
> There are a few changes in Chrome made over the last year or so that
> impact GWT development and debugging in various ways.
> https://gwt-review.googlesource.com/c/gwt/+/23500 fixes SDM (and
> cross origin apps) stack traces being lost, and unhandledrejection events
> are entirely lost in some cases.
> https://gwt-review.googlesource.com/c/gwt/+/23580 tracks a newer
> change in Chrome dev tools, where the unofficial Function.displayName
> property no longer works when debugging obfuscated code with GWT's
> -XmethodNameDisplayMode flag, and transitions to the standard 
> Function.name
> property instead.
>
>
> --
>
> IE8/IE9/IE10 removal
> Another thread on this mailing list
> 
> tracks the ongoing discussion of removing three end-of-life'd browsers 
> from
> GWT. It has been suggested that IE11 support remain for at least a little
> while longer. According to
> https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge,
> IE11 as a desktop application will no longer be supported after June 2022,
> though that may change, and even if it does not, it may make sense to
> continue support for some time after that.
>
> --
>
> Dropping Java 7 support, and upgrading Jetty 9 and HtmlUnit
> Building GWT itself with something newer than Java 8 is going to
> require additional work (see
> https://github.com/gwtproject/gwt/issues/9683), but the time has come
> to no longer support Java 7, and require 8 as the minimum version for
> building and using GWT. I have a work in progress patch
> 
> which upgrades both Jetty 9 and HtmlUnit to their latest respective
> versions in order to deal with several 

Re: [gwt-contrib] Re: Goodbye IE 8–9 

[Juan Pablo Gardella]

+1 drop IE 11 increases the effort to include new stuff. IE +11 can still
use GWT 2.9.0

On Thu, 30 Sept 2021 at 16:55, Vegegoku  wrote:

> I vote to even drop support for IE11.
>
> On Thursday, September 30, 2021 at 7:49:56 PM UTC+3 nilo...@gmail.com
> wrote:
>
>> I've just filed https://github.com/gwtproject/gwt/issues/9739, where a
>> workaround exists in java.util.Date that nearly doubles the time it takes
>> to parse date strings and build date objects. This workaround exists for
>> IE8 and IE9, as all more recent browsers implement the same behavior as we
>> already would expect. Dropping support for those two browsers would
>> simplify the code required here
>>
>> From the age of this thread and the discussion so far, it sounds like
>> there is interest in keeping IE11 still, but no one has spoke up about IE10
>> or below.
>>
>> Additionally, java.util.Random emulation was changed to require
>> Date.now(), which isn't available in IE8, so neither GWT 2.8.2 nor GWT
>> 2.9.0 are apparently compatible with IE8 anyway, at least in this small
>> way. This should give us some confidence (along with the lack of opposition
>> in this thread) that at least IE8 is definitely safe to drop.
>>
>> So, is there any objection at this time to dropping what remains of IE8,
>> IE9, and IE10 support from GWT? Then, we can reevaluate IE11 at some later
>> date, for GWT itself? Various migrated GWT modules have focused their
>> efforts on well-supported browsers, and are likely to only support IE11 by
>> accident anyway.
>>
>> On Friday, March 12, 2021 at 1:20:02 AM UTC-6 stuckagain wrote:
>>
>>> We still need IE11 support in the banking sector. We still have a
>>> majority of customers that use IE11 due to technical reasons (plugins
>>> needed for accessing secure token don’t install properly in Chrome without
>>> internet access amongst others).
>>>
>>> What do you mean with “next version of GWT” if that is 3.x then I don’t
>>> care at this point. We have been waiting for that release for a few years
>>> now. But 2.x releases should not drop IE11 support it is supposed to be a
>>> long-term supported version.
>>> On 12 Mar 2021, 07:54 +0100, bernhar...@schubec.com <
>>> bernhar...@schubec.com>, wrote:
>>>
>>> Hi all!
>>>
>>> I think IE11 support should be dropped soon if it blocks (or makes it
>>> difficult) to implement new features in the next version of GWT.
>>> I understand, that there are enterprises who still use IE11 internally,
>>> but developers who service such enterprises should use the current version
>>> of GWT, which is not going away. Nobody is forced to upgrade to the next
>>> version of GWT.
>>>
>>> Thanks,
>>> Berni
>>>
>>> tony.be...@gmail.com schrieb am Donnerstag, 11. März 2021 um 22:26:21
>>> UTC+1:
>>>
 IE 11 is still widely used inside corporations, because it is the only
 browser that supports Java applets, and applications such as Oracle
 e-Business Suite still use applets extensively (for Oracle forms). While
 that segment does not move very fast, it does not mean other unrelated
 groups within the same corporation are not updating GWT regularly. It is
 hard to generalize In a multinational company  with tens of thousands of
 employees.

 Regards

 Tony

 On Thu, Mar 11, 2021 at 9:49 AM Jens  wrote:

> Dropping IE 8-10 shouldn't really hurt. Companies that require it are
> probably not upgrading GWT in a fast pace anyways.
>
> However I wouldn't drop IE 11 anytime soon. IE 11 itself is tied to
> the lifecycle of Microsoft's operating systems, which means for Windows 10
> it is supported until 2025 (for now). So just because MS and Google drop
> support for IE 11 in some/all of their products, the browser itself is
> still generally supported by MS. So we should think twice before removing
> IE 11 from a library such as GWT, even if it means to decline/revert
> certain commits if they break IE 11. From own experience I have usually
> seen something around 8% of IE 11 usage in GWT based apps.
>
> However I am pretty sure more and more companies will announce
> dropping IE 11 this year or next year. With MS and Google starting, this
> could easily have a domino effect. However GWT also also strongly used
> internally inside companies so it might not have that much of an effect in
> that area.
>
> If we ditch IE 8-10 and only leaving gecko1_8 and safari, can't we
> kill them both as well and put them together? Are there so many 
> differences
> in code between both? From my work migrating GWT code to
> elemental2/JsInterop I had the feeling that only some minor stuff is
> different between both. So there shouldn't be that much overhead in code
> size and performance doing (cached) runtime checks instead.
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google
> Groups "GWT Contributors" 

Re: [gwt-contrib] Resolving cycle dependency between gwt-safehtml & gwt-safecss

[Juan Pablo Gardella]

+1 to merge them. It seems the simplest solution.

On Thu, 25 Jun 2020 at 17:23, Colin Alworth  wrote:

> One potential option could be moving the tests into gwt-safecss, and only
> release them together - the release process through sonatype will permit
> you to push more than one set of artifacts, test them in the staging repo,
> and then release to central together. That would imply using either local
> artifacts to build gwt-safecss (instead of pulling from central), or
> temporarily adding the staging repo to the pom.
>
> It does seem simpler to just merge to gwt-safehtml - especially since I
> doubt that gwt-safecss is often used by itself.
>
> On Thursday, June 25, 2020 at 3:19:05 PM UTC-5 juan_pablo_gardella wrote:
>
>> Not too much options I think, see
>> https://stackoverflow.com/questions/55429921/how-to-fix-cyclic-dependency-between-java-modules
>>
>> Maybe a new common shared module (maven artifact in this case) or merge
>> safehtml and safecss into a new one and let them deprecated.
>>
>> Juan
>>
>> On Thu, 25 Jun 2020 at 17:14, 'Frank Hossfeld' via GWT Contributors <
>> google-web-tool...@googlegroups.com> wrote:
>>
>>> To prepare GWT for j2cl we need to move the modules out of GWT, replace
>>> generators with ATP, etc. This is in progress and the first modules
>>> (SNAPSHOT) are released.
>>>
>>> Migrating gwt-safehtml and gwt-safecss runs into a problem, cause
>>> gwt-safehtml depends on gwt-safecss and gwt-safecss depends on
>>> gwt-safehtml. This is a serious issue, cause one can not be build and
>>> tested without the other.
>>>
>>> To solve this issue, we are looking for solutions.
>>>
>>> One solution might be to move the tests out of gwt-safehtml. But then
>>> gwt-safehtml needs to be build and deployed before the tests run and might
>>> be deployed with failing tests. That looks like a bad solution.  At the
>>> moment the idea is to move the sources and tests from gwt-safecss into
>>> gwt-safehtml and delete gwt-safecss. This will remove the cycle dependency
>>> between these two modules, but doing so, the module will be the first
>>> module that contains two old modules in one new.
>>>
>>> Any other ideas how to solve this issue?
>>>
>>> --
>>> 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-co...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a8d6c785-c8d9-4eba-8cc2-0b42ecac1124o%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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/8b4addde-bf52-4a88-b38f-fd2c0493f9f9n%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFscwn64KFDxxoqNx5hKRWCVQZ08HkS9GkbZvw6%3D%3D_5YcWA%40mail.gmail.com.

Re: [gwt-contrib] Resolving cycle dependency between gwt-safehtml & gwt-safecss

[Juan Pablo Gardella]

Not too much options I think, see
https://stackoverflow.com/questions/55429921/how-to-fix-cyclic-dependency-between-java-modules

Maybe a new common shared module (maven artifact in this case) or merge
safehtml and safecss into a new one and let them deprecated.

Juan

On Thu, 25 Jun 2020 at 17:14, 'Frank Hossfeld' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> To prepare GWT for j2cl we need to move the modules out of GWT, replace
> generators with ATP, etc. This is in progress and the first modules
> (SNAPSHOT) are released.
>
> Migrating gwt-safehtml and gwt-safecss runs into a problem, cause
> gwt-safehtml depends on gwt-safecss and gwt-safecss depends on
> gwt-safehtml. This is a serious issue, cause one can not be build and
> tested without the other.
>
> To solve this issue, we are looking for solutions.
>
> One solution might be to move the tests out of gwt-safehtml. But then
> gwt-safehtml needs to be build and deployed before the tests run and might
> be deployed with failing tests. That looks like a bad solution.  At the
> moment the idea is to move the sources and tests from gwt-safecss into
> gwt-safehtml and delete gwt-safecss. This will remove the cycle dependency
> between these two modules, but doing so, the module will be the first
> module that contains two old modules in one new.
>
> Any other ideas how to solve this issue?
>
> --
> 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/a8d6c785-c8d9-4eba-8cc2-0b42ecac1124o%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFsd7i9fZj5tXLTDN5hE0yCe%2BvtDuEt7Ydu%3DxafJe35jycQ%40mail.gmail.com.

Re: [gwt-contrib] Testing GWT 2.9.0 for release

[Juan Pablo Gardella]

I verified GWT 2.9.0-RC1 in one of my applications without issues. The
tests I could not complete due an ant issues to build the samples.

Juan

On Sun, 19 Apr 2020 at 22:01, Colin Alworth  wrote:

> We're having an issue related to the java7->java8 update, the build isn't
> properly including the full sources for the included sample projects. By
> itself, not a big deal, but it could imply that other assumptions of the
> ant build are broken too. I'm looking into it, we'll have an updated
> release candidate when we figure it out.
>
> https://github.com/gwtproject/gwt/issues/9682: The 2.9 candidate was cut
> before the java.io changes came in, so this will not be included in the
> first 2.9 at least, though will likely show up later (See the 4th point in
> this email).
>
> Removing validation: as a rule, the main GWT project rarely, if ever,
> removes anything within a major release. This is very deliberate, so that
> updating to the latest release (to fix security issues, to support
> newer/changing/breaking browsers, improve performance) is accessible to
> stable projects in maintenance mode, with no surprises. Since gwt-dev and
> gwt-user are strongly tied to each other, it isn't feasible to even suggest
> that someone update part of their project, but continue to use older jars
> (such as updating the compiler to fix some issue, but still keeping an old
> gwt-user so that the now-deprecated validation doesn't change or
> disappear). This is why each module that is being broken out will now live
> in its own git repo, own jar, and be versioned separately from the others.
> My best guess here is that we can try for a "minimal gwt-user" which just
> has enough to let the compiler work, and assume that developers switch to
> the org.gwtproject modules that they want, plus anything thirdparty like
> validation. That said, validation is basically the only thing that _isn't_
> ready for j2cl, and there is a small gwt-validation project that has gotten
> started that is compatible with both gwt2 and j2cl - do you have plans to
> finish https://gitlab.com/ManfredTremmel/gwt-bean-validators/-/issues/3?
> Both topics (further modularizing gwt-user, and apt for validation) are
> probably better discussed in another thread, or in gitter.
>
> CL 19800: Agreed, sucks that this fell through the cracks. Two thoughts:
> lets get that into gwt-i18n as soon as possible, and lets try to land that
> patch after 2.9.0 is cut and shipped. The plan is that 2.9.x gets updated
> regularly (6-8 weeks sort of thing) with any changes, and marked with a
> date rather than just an occasional version.
>
> --
> 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/9b91b87d-4ff7-483a-99cc-356bb4ce00d9%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFscYV4and2TSffgBA65x-hwucVkpi51Opzex3AtZ0WU%3D5w%40mail.gmail.com.

Re: [gwt-contrib] Testing GWT 2.9.0 for release

[Juan Pablo Gardella]

Hi Colin,

Could you please share the spreadsheet again?

Juan

On Mon, 13 Apr 2020 at 23:43, Colin Alworth  wrote:

> Hi all,
> We have a build ready to test for GWT 2.9.0, and are looking for
> volunteers to verify that things are behaving properly on a variety of
> platforms. If you have an hour or two free and can help us out, we would
> appreciate it.
>
> We're hoping for a cross-section of testing that verifies
>  * JVM version: 8, 11, 14
>  * Operating System: Linux, OS X, Windows (8, 8.1, 10)
>  * Browser: Chrome, Firefox, Safari, IE11, Edge
>
> If a tester has access to more than one of these at a time, the tests will
> probably go more quickly than two individuals testing the same setup.
> Please note that while Microsoft still provides virtual machines for
> testing purposes, only Windows 10 appears to be available, though with both
> IE11 and Edge (
> https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/).
>
> Please send me an email off-list with the various options you are able to
> test, and I'll get you on the testing spreadsheet.
>
> Thanks!
>
> --
> 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/c0e7162a-5217-4e89-8c50-ee3c051202c2%40googlegroups.com
> 
> .
>

-- 
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/CA%2BkiFseb94LNZo8-vqXD6KTTHApRq8jAAnL7gW18EoTHygzz3w%40mail.gmail.com.

Re: [gwt-contrib] Last call for GWT 2.8.2 patches, and testers needed!

[Juan Pablo Gardella]

How can I contribute to test?

On Tue, 3 Oct 2017 at 07:28 Colin Alworth  wrote:

>

-- 
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/CA%2BkiFse7CgsakT%2B7OGzLt_3gjnAF2YOTt2dij5sFWfH1gih3Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT Plugin v3.0 and tbroyer maven integration ?

[Juan Pablo Gardella]

Did you check if it works by putting in Application.gwt.xml in
src/main/java instead of src/main/resources?

On Fri, 23 Dec 2016 at 06:48 stuckagain  wrote:

>
> Living behind a corporate firewall is hell as I cannot get my hands on the
> GWT plugin (I have a support case open for now 3+ months) unless I build it
> myself and produce a zip file of the eclipse plugin and somehow get it on
> my dev computer.
>
> I tried to build the 3.0-SNAPSHOT release on my computer at home but that
> one fails with:
>
> [ERROR] Failed to resolve target definition
> /Users/home/Projects/gwt-eclipse-plugin/eclipse/mars/gwt-eclipse-mars.target:
> Failed to load p2 metadata repository from location
> https://storage.googleapis.com/gcloud-for-eclipse-testing/: No repository
> found at https://storage.googleapis.com/gcloud-for-eclipse-testing. ->
> [Help 1]
>
> [ERROR]
>
> I tried to use the build on the brandon-release branch. Building went
> fine, I managed to install the plugin in my eclipse installation.
> But I can't get very far with starting the codeserver from eclipse.
>
> I am using the tbroyer maven plugin in a multi module maven project and I
> am using the module.gwt.xml approach that will generate the real gwt.xml
> file during build.
> When I try to launch the codeserver it just complains that it cannot find
> the Application.gwt.xml file in the classpath, even though the classpath is
> correct. So my guess that there is something wrong with the m2eclipse
> integration ? Since it does not appear to be generating the gwt.xml before
> launching as it should.
>
> How can I progress this painful exercise ?
> How can I get SNAPSHOT to properly build on the master branch ?
> How far does the tbroyer plugin support go ?
>
> --
> 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/54829475-70db-4e76-9a31-76d7c54cd9ac%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/CA%2BkiFsfgTvUVy3vZVTcnTXGrGMd5sCA_cQD5xPGpuhBzWr8Vzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.0-beta1 available for testing

[Juan Pablo Gardella]

Hi contributors,

I've created a google doc  with full GWT 2.8.0
release notes. It's divided by features/components and links for each
commit. I didn't put reverted commits, and fixes over features like
JSInterop. Everyone can put comments. It could be added later at GWT
official documentation once gwt 2.8.0 is completed.

Juan

On 7 December 2015 at 11:15, István Horváth  wrote:

> ok, i have PR for this, i hope it fits Google's needs.
>
> 2015. december 7., hétfő 15:47:50 UTC+1 időpontban Julien Dramaix a
> következőt írta:
>>
>> Feel free to fill a patch for that :)
>>
>> On Mon, Dec 7, 2015 at 2:28 PM István Horváth  wrote:
>>
>>> it would nice to have if you update the release notes page with exact
>>> dates on all of the version on both the links and the linked details too.
>>>
>>> http://www.gwtproject.org/release-notes.html
>>>
>>>
>>> 2015. december 4., péntek 10:51:13 UTC+1 időpontban Daniel Kurka a
>>> következőt írta:

 Hi all,

 we just finished testing for GWT 2.8.0-beta1. You can either download
 it from goo.gl/62SeR5 or from maven central.

 Release notes can be found here
 
 .

 Please start testing and let us know about any issues you encounter by
 either discussion here or filing bugs on github
 .

 -Daniel

>>> --
>>> 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/06401611-3eeb-4647-9fca-69459939aa8d%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/5ac770a2-db1c-4676-b167-8632289decae%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/CA%2BkiFseLrH5LPYM%3DkmqBFNrjqJOuvq28ZC9vvpfiM6xcKxNAYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8.0-beta1 available for testing

[Juan Pablo Gardella]

It will be very useful to make gwt-servlet compatible with java 6

On 4 December 2015 at 17:41, Jens  wrote:

>
> Is it intentional/necessary that gwt-servlet.jar is compiled for Java 7
>> and not Java 6?
>>
>
> gwt-servlet.jar isn't really compiled, its just assembled. The build
> script compiles gwt-dev and gwt-user using Java 7 as minimum and then
> gwt-servlet.jar is created by pulling in a subset of already compiled
> classes of gwt-user and gwt-dev. That means gwt-servlet.jar also requires
> Java 7. So generally its intentional.
>
> Also as soon as we land Java 8 API emulations GWT will be compiled using
> Java 8 which would mean gwt-servlet.jar also requires Java 8. Its probably
> not possible to keep gwt-servlet.jar compatible to Java 7 because as soon
> as we add java.time emulation to GWT we probably also add GWT-RPC custom
> field serializers for Java 8 classes like LocalDate, etc.
>
> -- J.
>
> --
> 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/afbc2b40-5a48-4e6d-960e-e59d46a81936%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/CA%2BkiFsfRoq70DtV%3DvMNc1PB4k6sOURtLJxeH5YzQ%3Du163VPdLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.8 Release

[Juan Pablo Gardella]

Great work! Thanks. Is there any release note to GWT 2.8?

On 23 October 2015 at 01:55, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> In the last few months, we had important progress on JsInterop and finally
> it looks like we will be able to start the release process for 2.8 in a few
> weeks. So if you believe a patch needs to be part of the RC release, this
> is a good time to engage.
>
> I know there will be questions about Java8 so here are some answers:
> Language features wise, we are feature complete for long time. However
> plenty of new APIs, most significantly streams, is not emulated. The
> release will only include the subset of the APIs that is contributed by the
> community so it is in the hands of open source contributors.
> We may also do a 2.8.x release with bug fixes that includes latest
> contributions to emulation.
>
> Let me know if you have any questions.
>
> Cheers.
>
> --
> 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/CAN%3DyUA3eb9YqQsxdZXHPtzo6uwyJnSDMcdTpfKj-B%2BRzpJ7pjw%40mail.gmail.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/CA%2BkiFscb-Kg8nvF4j0J%3DwA-Oba_GTb2fo7XpLDo_n4ibcEDktQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Git rebase

[Juan Pablo Gardella]

Hi contributors,

I did a commit (A) and pushed the changes to be reviewed. After that I did
some pulls and merges locally. Then my history contains the merge M:


M
|  \
B |
|  /
A

I completed my changes and with some rebase commands I was able to have:

A
|
B

But when I tried to push the changes I saw the following error:

remote: Processing changes: refs: 1, done
remote:
remote: ERROR:  In commit xxx
remote: ERROR:  author email address x...@xxx.com
remote: ERROR:  does not match your user account.
remote: ERROR:
remote: ERROR:  The following addresses are currently registered:
remote: ERROR:x...@gmail.com
remote: ERROR:
remote: ERROR:  To register an email address, please visit:
remote: ERROR:  https://gwt-review.googlesource.com/#/settings/contact
remote:
remote:


Do you know how to solve this problem?

Thanks

-- 
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/CA%2BkiFscdDWBsUVVqKDiVMVC_%2B%3DY0vQW1MzgbW49DCaw8kTTDEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Git rebase

[Juan Pablo Gardella]

My author is correct, but after the rebase the error is related to a commit
that I'm not owner. I had to pull the repository again and fetch my changes
again, after that, I made the changes and pushed them. I don't know how to
solve that without pull the full repository again.

On 24 June 2015 at 07:06, Jens jens.nehlme...@gmail.com wrote:

 As the error message says your git commit has an author whose email
 address is not the one you use with your Gerrit user account. To update the
 author of your commit you need to do something like:
 http://stackoverflow.com/a/3042512

 -- J.

 --
 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/3e2aeed3-33d4-49d6-bde6-39f12ae57432%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/3e2aeed3-33d4-49d6-bde6-39f12ae57432%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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/CA%2BkiFsf-Hejeha_AO-yFSthC0edZo_03%2Bh80pO%3D8Yr_tWVJsuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Git rebase

[Juan Pablo Gardella]

Thanks a lot Jens, I will do that in my next contribution.

On 24 June 2015 at 07:35, Jens jens.nehlme...@gmail.com wrote:


 My author is correct, but after the rebase the error is related to a
 commit that I'm not owner. I had to pull the repository again and fetch my
 changes again, after that, I made the changes and pushed them. I don't know
 how to solve that without pull the full repository again.


 Oh seems like your rebase action has also rewritten some commits that you
 don't own. Of course thats bad.

 I would advice you to always create a local branch for each contribution.
 Then when you want to incorporate changes of master into your local
 contribution branch you switch back to master branch, pull changes and then
 rebase your local contribution branch on top of master. In the process of
 rebasing you might need to fix conflicts and then continue rebasing.

 That way you avoid merge commits and you can work on multiple
 contributions while others are still in review. You can also have multiple
 contributions in one branch if they depend on each other. For example I
 have a java8-emul branch which provides java.util.function emulation and
 that same branch also has commits for emulating java.util.Optional and
 others as they depend on java.util.function.

 -- J.

 --
 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/9a94a66a-3593-48b2-aec5-0e23c0ab6111%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/9a94a66a-3593-48b2-aec5-0e23c0ab6111%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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/CA%2BkiFsfP7CZAJuxFykHz4ycCD_roxo9_CFo%2BgrfUB23c8MXF5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Upcoming overhaul to JsInterop annotations in preparation towards v1.0 release

[Juan Pablo Gardella]

Why export is defaulted to false?

On 19 May 2015 at 19:21, 'Goktug Gokdogan' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Here is the comparison chart:


 @JsExport @JsType

 class MyClass {}

 @JsType(exports=ALL)

 class MyClass {}

 @JsExport

 class MyClass {}

 @JsType(exports=STATIC_MEMBERS)

 class MyClass {}

 @JsExport(“Name”)

 class MyClass {}

 @JsType(name=”Name”, exports=STATIC_MEMBERS)

 class MyClass {}

 @JsExport(“Name”) @JsType

 class MyClass {}

 @JsType(name=”Name”, exports=ALL)

 class MyClass {}

 @JsType

 class MyClass {}

 @JsType(exports=INSTANCE_MEMBERS)

 class MyClass {}

 @JsType

 interface MyInterface{}

 @JsType(exports=INSTANCE_MEMBERS)

 interface MyInterface{}

 @JsType

 interface ImportedLibrary{}

 @JsType

 interface ImportedLibrary{}

 @JsType

 interface ImportedLibraryCallback{}

 @JsType(exports=INSTANCE_MEMBERS)

 interface ImportedLibraryCallback{}

 @JsExport

 SomeConstructor{}
 @JsExport

 static void someStaticMethod{}
 @JsExport

 static Object someStaticField;

 @JsConstructor(export=true)

 SomeConstructor{}
 @JsMethod(export=true)

 static void someStaticMethod{}
 @JsProperty(export=true)

 static Object someStaticField;

 @JsExport(“someName”)

 static void someStaticMethod{}
 @JsExport(“someName”)

 static Object someStaticField;

 @JsMethod(name=”someName”, export=true)

 static void someStaticMethod{}
 @JsProperty(name=”someName”, export=true)

 static Object someStaticField;

 @JsNoExport

 static void someStaticMethod{}

 @JsMethod(export=false) or @JsIgnore

 static void someStaticMethod{}

 @JsNoExport

 void someMethod{}

 @JsIgnore

 void someMethod{}

 @JsProperty

 void someMethod{}

 @JsProperty

 void someMethod{}

 @JsProperty(“someName”)

 int someField;
 @JsProperty(“someName”)

 void someMethod{}

 @JsProperty(name = “someName”)

 int someField;
 @JsProperty(name = “someName”)

 void someMethod{}

 On Tue, May 19, 2015 at 3:17 PM, Goktug Gokdogan gok...@google.com
 wrote:

 Thanks for the nice summary Ray.

 This is still work in progress but here is the tentative list of
 annotations and details of the new semantics. Please play with it and
 continue making suggestions.

 *@JsConstructor*
 JsConstructor marks a constructor so that it will be the constructor
 function for the JavaScript type. Note that, there could be only one
 JsConstructor in a type and all other constructors should be delegating to
 it.

 public @interface JsConstructor {
   /**
* If a constructor is exported, then it will be not be pruned by the
 compiler.
*/
   boolean export() default false;
 }

 *@JsMethod*
 JsMethod marks a method in a type as a method that will be directly
 translated into a JavaScript method without any obfuscation to its name.
 Note that, while instance members are slotted in the prototype, class
 members will be defined under the constructor function of the type.

 public @interface JsMethod {
   /**
* Customizes the name of the method in generated JavaScript. If not
 provided, the Java name will
* be used.
*/
   String name() default ;

   /**
* If a method is exported, then it will be not be pruned by the
 compiler. Note that if the class
* is pruned then instance members will also be pruned even they are
 exported (i.e. exporting
* instance members doesn't prevent class pruning).
*/
   boolean export() default false;
 }

 *@JsProperty:*
 JsProperty marks a field in a type as a method that will be directly
 translated into a javascript property without any obfuscation to its name.
 If it is applied to a method, it will be treated as a property accessor.
 As a result, instead of translating method calls to JsProperty methods as
 method calls in JS, they will be translated as property lookups. When a
 JsProperty method implemented by a Java class, such methods will be
 generated as custom property setter and getter in JavaScript, hence the
 property access will trigger the execution of the matching getter or setter
 methods.

 JsProperty follows JavaBean style naming convention to extract the
 default property name. If the JavaBean convention is not followed, the name
 should be set explicitly. For example:
   @JsProperty getX() or @JsProperty isX() translates as ttthis.x/tt
   @JsProperty setX(int y) translates as ttthis.x=y/tt

 Note that, while non-static member are slotted in the prototype, static
 members will be defined under the constructor function of the type.

 public @interface JsProperty {
   /**
* Customizes the name of the member in generated javascript. If none
 is provided;
* p
* liif it is field, the simple Java name will be used.
* liif it is a method, the name will be generated based on JavaBean
 conventions.
*/
   String name() default ;

   /**
* If a method is exported, then it will be not be pruned by the
 compiler. Note that if the class
* is pruned then non-static members will also be pruned even they are
 exported 

Re: [gwt-contrib] Open reviews

[Juan Pablo Gardella]

Any thoughts? Who are able to take reviews?

On 12 May 2015 at 18:35, Richard Wallis rdwal...@gmail.com wrote:

 Anyone want to review my patch to the scheduler?
 https://gwt-review.googlesource.com/#/c/11510/

 Also it would be good if patches automatically had someone assigned to
 review them.  If the patch falls outside a reviewer's domain then they can
 transfer it to someone else.


 On Tue, May 12, 2015 at 11:16 PM, Juan Pablo Gardella 
 gardellajuanpa...@gmail.com wrote:

 Hi contributors,

 I would like to thanks for your great work and for the passion that you
 put on GWT. I know you are very busy but it's frustrating to spend time in
 some patch and then nothing happen. There are a lot of open reviews
 https://gwt-review.googlesource.com/#/q/status:open. That kind of
 things prevent developers to spend time in patches in the future.

 I say that because I want more contributions for GWT.

 Regards,
 Juan

 --
 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/CA%2BkiFse4iTAoZUKzyaq-4iVFznXXkPM9k1nEfd6-tsQutuk7zg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse4iTAoZUKzyaq-4iVFznXXkPM9k1nEfd6-tsQutuk7zg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/CAEqaEVhfxgWe450NCqDxEh2ENZLksSxMY5nwj%3D8-9hR3e85zEQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEqaEVhfxgWe450NCqDxEh2ENZLksSxMY5nwj%3D8-9hR3e85zEQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/CA%2BkiFsff3efEF6KSGD%2BdvwSY0mQnwvHG%3Djx8xR%2BmT6tAr0%3DY9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Open reviews

[Juan Pablo Gardella]

Hi contributors,

I would like to thanks for your great work and for the passion that you put
on GWT. I know you are very busy but it's frustrating to spend time in some
patch and then nothing happen. There are a lot of open reviews
https://gwt-review.googlesource.com/#/q/status:open. That kind of things
prevent developers to spend time in patches in the future.

I say that because I want more contributions for GWT.

Regards,
Juan

-- 
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/CA%2BkiFse4iTAoZUKzyaq-4iVFznXXkPM9k1nEfd6-tsQutuk7zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] How to include changesets to an existing gerrit review?

[Juan Pablo Gardella]

Thanks Daniel!

On 9 March 2015 at 11:55, 'Daniel Kurka' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 You make the changes in your local git client and amend the commit: 'git
 commit --amend'

 Then you just push to gerrit: 'git push origin HEAD:refs/for/master' and
 this will update the review.

 On Mon, Mar 9, 2015 at 3:49 PM, Juan Pablo Gardella 
 gardellajuanpa...@gmail.com wrote:

 Hi all,

 I've started a gerrit review and I have to add to add some improvements
 due some review observations. How I can include the changes in the same
 gerrit review?

 Thanks

 --
 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/CA%2BkiFsfGwo0sk_h2S9nTPwNUs6GQsd14Fk0n8uog04bBkwf4dQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFsfGwo0sk_h2S9nTPwNUs6GQsd14Fk0n8uog04bBkwf4dQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




 --
 Google Germany GmbH
 *Dienerstr. 12*
 *80331 München*

 Registergericht und -nummer: Hamburg, HRB 86891
 Sitz der Gesellschaft: Hamburg
 Geschäftsführer: Graham Law, Katherine Stephens

 --
 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/CALLujipqsX8temc_0%2B0MQj2kgppCJE2n67AhFv32tR2P_jeSZA%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipqsX8temc_0%2B0MQj2kgppCJE2n67AhFv32tR2P_jeSZA%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/CA%2BkiFsehqfVbOaujh7EZJgF1W26ssdHuJTkL6PuFHSgos%2Bivdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] How to include changesets to an existing gerrit review?

[Juan Pablo Gardella]

Hi all,

I've started a gerrit review and I have to add to add some improvements due
some review observations. How I can include the changes in the same gerrit
review?

Thanks

-- 
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/CA%2BkiFsfGwo0sk_h2S9nTPwNUs6GQsd14Fk0n8uog04bBkwf4dQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] com.google.gwt.dev.SourceSaver cannot be compiled with java6

[Juan Pablo Gardella]

Hi team,

I've just imported gwt-dev in Eclipse and I saw there is only one class
that doesn't compile: *com.google.gwt.dev.SourceSaver*:


line 213:try (InputStream resourceAsStream =
Resources.asByteSource(resource).openStream();
 OutputStream out = dest.openForWrite(destPrefix + path);) {
  ByteStreams.copy(resourceAsStream, out);
 }

If I change to the compiler compliance to 1.7 it works. Should the
eclipse/README.txt be updated?

eclipse/README.txt:
 Compiler settings 
Window-Preferences-Java-Compiler
Set the compiler compliance level to 1.6.

Juan

-- 
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/CA%2BkiFse3mu9hURYFcPGeFP5uCWgf-c1SM2DzEFSSVXs6m86qUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] com.google.gwt.dev.SourceSaver cannot be compiled with java6

[Juan Pablo Gardella]

Done: https://gwt-review.googlesource.com/#/c/11970/

On 2 March 2015 at 11:53, 'Daniel Kurka' via GWT Contributors 
google-web-toolkit-contributors@googlegroups.com wrote:

 Yes the readme needs to be updated. Trunk does not support java6 anymore.
 Mind sending a patch?

 On Mon, Mar 2, 2015 at 3:38 PM, Juan Pablo Gardella 
 gardellajuanpa...@gmail.com wrote:

 Hi team,

 I've just imported gwt-dev in Eclipse and I saw there is only one class
 that doesn't compile: *com.google.gwt.dev.SourceSaver*:


 line 213:try (InputStream resourceAsStream =
 Resources.asByteSource(resource).openStream();
  OutputStream out = dest.openForWrite(destPrefix + path);) {
   ByteStreams.copy(resourceAsStream, out);
  }

 If I change to the compiler compliance to 1.7 it works. Should the
 eclipse/README.txt be updated?

 eclipse/README.txt:
  Compiler settings 
 Window-Preferences-Java-Compiler
 Set the compiler compliance level to 1.6.

 Juan

 --
 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/CA%2BkiFse3mu9hURYFcPGeFP5uCWgf-c1SM2DzEFSSVXs6m86qUg%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CA%2BkiFse3mu9hURYFcPGeFP5uCWgf-c1SM2DzEFSSVXs6m86qUg%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




 --
 Google Germany GmbH
 *Dienerstr. 12*
 *80331 München*

 Registergericht und -nummer: Hamburg, HRB 86891
 Sitz der Gesellschaft: Hamburg
 Geschäftsführer: Graham Law, Katherine Stephens

 --
 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/CALLujiociaeGBxnQA1DSXi9_Jot8Z4hNeF--iadUcY1mz6O5UQ%40mail.gmail.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiociaeGBxnQA1DSXi9_Jot8Z4hNeF--iadUcY1mz6O5UQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/CA%2BkiFsdHmk8b7mX9DJ7YV22qKzV92wzKm%2BpQSC7q1Jh%3DzssfEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags

[Juan Pablo Gardella]

Thanks for sharing Jérémie. Good to know.

On 21 October 2014 09:32, Jérémie Gottero jeremiegott...@gmail.com wrote:

 Do we have an easy way to exclude these folders to see if it improves
 things?


 Quick and dirty: I overrode the descendToFindResources method to exclude
 .svn files (note that the file is excluded before isDirectory/isFile calls,
 avoiding an extra i/o):

 File[] children = dir.listFiles();
 for (File child : children) {
   if (child.getName().equals(.svn)) // hardcoded filter here
   continue;
   String childPath = dirPath + child.getName();
   if (child.isDirectory()) {

 Reload time goes down from 2,8s to 1,1sec. The ability to filter files
 here could lead to interesting speed improvements.

 Another possible improvement: I got 4874 calls to file.lastModified() in a
 single browser refresh, for 2088 unique files. Caching the result per run
 could avoid 50% i/o and reload time would go below 1s. I have no idea if
 it's realistic/easy to do though, I havent dug in the code ;)

 --
 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/b052327f-8538-4598-b4fb-740cd16d2deb%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/b052327f-8538-4598-b4fb-740cd16d2deb%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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/CA%2BkiFse_4M3ZqrOa2D%2BdQfVhmWvxXABFH7F7y-KkNXKu5HLxcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

[Juan Pablo Gardella]

Java7 is fine for development

On 11 September 2014 15:13, Koen Maes k...@koma.be wrote:

 Java7 is just fine for me...

 On Thursday, September 11, 2014 7:50:53 PM UTC+2, Daniel Kurka wrote:

 Hi all,

 while bringing GSS support into GWT, I discovered that the closure
 styleheets compiler actually requires Java7.
 This means that we either have to do a back port of the compiler (I
 haven't looked at it seriously) or require Java7 for development with GWT
 (probably only if you are using CssResource).

 I really like your input on this and if I do not hear any strong
 objections, I will go ahead with using the Java7 version of closure
 stylesheets and thus we will require Java7 for GWT development.

 Note: This does not impact deployment of any GWT apps. You can still run
 a GWT app on a Java6 container, this will only affect developers on their
 machines.

 -Daniel

  --
 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/50627301-f84d-4cdd-888a-8db96d387b86%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/50627301-f84d-4cdd-888a-8db96d387b86%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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/CA%2BkiFsf-EkRyuf5csMbDdWyk%2BvvwCSABUQDw2x2esD1gg-%2BK9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM -XcompilePerFile: initial feedback

[Juan Pablo Gardella]

Great news!! Thanks a lot for the effort.


On 29 August 2014 13:02, Ivan Markov ivan.mar...@gmail.com wrote:

 BTW using a more recent laptop seems to make a difference and nearly
 doubles the performance:
 MacBook Pro model 2013 (I7 2.7 GHz):
 - 2 to 3 seconds for recompiling changes to a single file
 - 2 to 3 seconds for linking
 - Changes to more types of course again results in a growth of the
 recompilation time; this time it is 8 instead of 13 seconds for the same
 set of around 10 changed files. Linking still 3 seconds.

 I think you are getting there!

  --
 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/c646cebb-005a-42fd-9f9d-62334e1a3189%40googlegroups.com
 https://groups.google.com/d/msgid/google-web-toolkit-contributors/c646cebb-005a-42fd-9f9d-62334e1a3189%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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/CA%2BkiFsckH3PPtw8ACwCPeJ%2BMecmyOr1vRLVsMOQ_C_VfM7HyiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Next Contributor Hangout

[Juan Pablo Gardella]

Thanks for sharing! Great work guys


2014-02-11 19:05 GMT-03:00 Goktug Gokdogan gok...@google.com:

 Link: https://www.youtube.com/watch?v=5PzpQg51uno


 On Tue, Feb 11, 2014 at 1:26 PM, Bhaskar Janakiraman 
 bjanakira...@google.com wrote:

 Recorded session is now on-line.
 Bhaskar


 On Friday, January 24, 2014 11:05:31 PM UTC-8, Bhaskar Janakiraman wrote:

 Hi Folks,
 The next contributor hangout will be on Wednesday, January 29, from
 10.45am to 11.30am PST. As before, please send me email (bjanakiraman at
 google) if you have something to discuss and want to participate in person,
 and I'll send you an invite.

 Agenda:
 Progress update on features for next GWT release.
 Any patches in progress that needs discussion.

 The session will be recorded and made available via the GWT G+ 
 pagehttps://plus.google.com/u/1/b/116516353752856283537/116516353752856283537/posts
 .

 Thanks,
 Bhaskar

  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Juan Pablo Gardella]

Thanks Colin


2013/12/9 Colin Alworth niloc...@gmail.com

 This system property isn't listed when either dev mode or the compiler
 runs because it is a system property, not a program arg. It should be
 provided with the other VM args when you start Java. These aren't listed as
 part of the normal properties, but are documented here:
 http://code.google.com/p/google-web-toolkit/wiki/JavaSystemPropertiesAndGwt

 We probably should migrate that table (and expand it?), but for the most
 part these are used to tweak internals that shouldn't normally be needed.
 In the case of the issue I'm pointing out with java6, it appears that this
 issue is only due to a build problem when the RC was originally compiled.
 The only other flag I use in the list with any regularity is
 gwt.jjs.traceMethods, which lets you see what the compiler is doing with
 each method as it works.


 On Sun, Dec 8, 2013 at 5:28 PM, Juan Pablo Gardella 
 gardellajuanpa...@gmail.com wrote:

 Thanks Thomas!


 2013/12/8 Thomas Broyer t.bro...@gmail.com



 On Sunday, December 8, 2013 2:12:31 PM UTC+1, Thomas Broyer wrote:


 On Saturday, December 7, 2013 7:42:42 PM UTC+1, juan_pablo_gardella
 wrote:

 HostedMode appears in http://www.gwtproject.org/doc/latest/
 DevGuideCompilingAndDebugging.html at the section Development Mode
 Options.


 Will fix.


 See https://gwt-review.googlesource.com/5651

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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
 .
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.




 --
 218.248.6165
 niloc...@gmail.com

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Juan Pablo Gardella]

Thanks Thomas!


2013/12/8 Thomas Broyer t.bro...@gmail.com



 On Sunday, December 8, 2013 2:12:31 PM UTC+1, Thomas Broyer wrote:


 On Saturday, December 7, 2013 7:42:42 PM UTC+1, juan_pablo_gardella
 wrote:

 HostedMode appears in http://www.gwtproject.org/doc/latest/
 DevGuideCompilingAndDebugging.html at the section Development Mode
 Options.


 Will fix.


 See https://gwt-review.googlesource.com/5651

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Juan Pablo Gardella]

Thanks for the link Thomas, but as you said was updated in 2010. HostedMode
appears in
http://www.gwtproject.org/doc/latest/DevGuideCompilingAndDebugging.html at
the section Development Mode Options.




2013/12/7 Thomas Broyer t.bro...@gmail.com



 On Saturday, December 7, 2013 12:52:12 AM UTC+1, juan_pablo_gardella wrote:

 Thanks Colin, it seems this parameter disable some performance
 improvements:

  GWT attempts to load pre-compiled GWT module archives (.gwtar files) to
 increase performance. Consequently, building GWT examples shipped with this
 release fails with the IBM implementations of the Java Developement Kit
 (both 1.6 and 1.7). To work around the issue, use the
 -Dgwt.usearchives=false parameter with gwt-maven-plugin to disable loading
 of the pre-compiled archives.


 Source: https://bugzilla.redhat.com/show_bug.cgi?id=919447

 And this argument is not listed in java -cp gwt-dev.jar
 com.google.gwt.dev.HostedMode


 This only lists arguments, and gwt.userarchives is a system property (BTW,
 HostedMode ?!?!?)
 I think someone really should update
 https://code.google.com/p/google-web-toolkit/wiki/JavaSystemPropertiesAndGwt
 I'll try to do it if I find time (and remember about it)

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: 2.6.0-rc3

[Juan Pablo Gardella]

Thanks Colin, it seems this parameter disable some performance improvements:

GWT attempts to load pre-compiled GWT module archives (.gwtar files) to
increase performance. Consequently, building GWT examples shipped with this
release fails with the IBM implementations of the Java Developement Kit
(both 1.6 and 1.7). To work around the issue, use the
-Dgwt.usearchives=false parameter with gwt-maven-plugin to disable loading
of the pre-compiled archives.


Source: https://bugzilla.redhat.com/show_bug.cgi?id=919447

And this argument is not listed in java -cp gwt-dev.jar
com.google.gwt.dev.HostedMode

Thanks


2013/12/6 Colin Alworth niloc...@gmail.com

 Workaround: add -Dgwt.usearchives=false  to your jvm args when invoking
 the tests or dev mode. From maven this uses the extraJvmArgs param:
 http://mojo.codehaus.org/gwt-maven-plugin/compile-mojo.html#extraJvmArgs.


 On Friday, December 6, 2013 1:03:57 AM UTC-6, Roberto Lublinerman wrote:

 It seems that we need to build the release with -sourceLevel 6 for it to
 work with Java 6.


 On Thu, Dec 5, 2013 at 10:43 PM, Colin Alworth nilo...@gmail.com wrote:

 Sorry for being unclear - I'm building/testing an application that makes
 use of GWT while still on Java6, not building/testing GWT itself. I'm
 trying to sanity test rc3 as a candidate for a final release of 2.6.0, and
 as far as my testing goes, this is the only point it is failing.

 To clarify the point about the references to Matthew's machine, unzip
 the gwt 2.6.0-rc3 download on code.google.com, unpack the gwt-user.jar
 file, and try this:

 $ strings com/google/gwt/core/Core.gwtar  | grep file | head
 fileNameq
 bfile:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/
 google/gwt/core/client/AsyncProvider.javat
 fileNameq
 ]file:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/
 google/gwt/core/client/Callback.javat
 fileNameq
 jfile:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/
 google/gwt/core/client/CodeDownloadException.javat
 fileNameq
 ]file:/usr/local/google/home/mdempsky/wd/gwt/user/src/com/
 google/gwt/core/client/Duration.javat
 fileNameq
 fileNameq


 On Friday, December 6, 2013 12:10:10 AM UTC-6, Roberto Lublinerman wrote:

 Hi Colin,

 Did you do ant clean? I find it strange that the resource points to
 Matthew's hard drive, as if Impl was precompiled by him (and in that case
 probably is consistent that the version is 51.0).

 I build from scratch in my laptop (only has java 1.6) and builds and
 tests run fine. Is there a specific application that you are trying to
 build?




 On Thu, Dec 5, 2013 at 9:23 PM, Colin Alworth nilo...@gmail.comwrote:

 I'm still running into trouble with the major version of the compiled
 classes being 51, so I'm unable to gwt 2.6.0-rc3 to work under jdk 1.6. As
 before, I was able to confirm that the actual .class files are compiled
 correctly, but yet I get fatal errors in attempting to run dev mode.
 Testing so far is on a mac with 1.6.0_65:

 $ java -version
 java version *1.6.0_65*
 Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
 Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)

 $ javap -v com.google.gwt.core.client.impl.Impl | head
 Compiled from Impl.java
 public final class com.google.gwt.core.client.impl.Impl extends
 java.lang.Object
   SourceFile: Impl.java
   InnerClass:
public abstract #77= #76 of #170; //UncaughtExceptionHandler=class
 com/google/gwt/core/client/GWT$UncaughtExceptionHandler of class
 com/google/gwt/core/client/GWT
   minor version: 0
   major version: *50*
   Constant pool:
 const #1 = Method#61.#163;//  java/lang/Object.init:()V
 const #2 = Field#55.#164;//  com/google/gwt/core/client/imp
 l/Impl.unloadSupport:Lcom/google/gwt/core/client/impl/UnloadSupport;

 When in dev mode, I've seen this error:
 22:44:37.233 [ERROR] [com.example.SampleProject] Unable to load module
 entry point class null (see associated exception for details)
 java.lang.UnsupportedClassVersionError: 
 com/google/gwt/core/client/impl/Impl
 : Unsupported major.minor version 51.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:471)
 at com.google.gwt.dev.shell.CompilingClassLoader.findClass(Comp
 ilingClassLoader.java:1121)
 at com.google.gwt.dev.shell.CompilingClassLoader.loadClass(Comp
 ilingClassLoader.java:1194)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:249)
 at com.google.gwt.dev.shell.ModuleSpace.loadClassFromSourceName(
 ModuleSpace.java:670)
 at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.
 java:359)
 at com.google.gwt.dev.shell.OophmSessionHandler.loadModule(Ooph
 mSessionHandler.java:200)
 at 

Re: [gwt-contrib] Rebinding Methods improvement proposal and working prototype

[Juan Pablo Gardella]

Thanks Andrés! Great work


2013/11/28 Andrés Testi andres.a.te...@gmail.com

 The last 3 months I have been working on a GWT Improvement Proposal
 inspired by the idea of Ray Cromwell for Relaxing constraints on
 GWT.create()http://timepedia.blogspot.com.ar/2009/03/relaxing-constraints-on-gwtcreate.html.
  I wrote a technical document and implemented it as a fork
 of GWT master at GitHubhttps://github.com/andrestesti/gwt-rebindingmethods
 .
 As a quick example of what is possible to do with Rebinding Methods, you
 can look at the hellorebinding 
 samplehttps://github.com/andrestesti/gwt-rebindingmethods/blob/master/samples/hellorebinding/src/com/google/gwt/sample/hellorebinding/client/MainWidget.java#L39
 :

  public MainWidget() {
 /*
  * No boilerplate required to bind user interfaces.
  */
 initWidget(UiBinders.createAndBindUi(Widget.class, MainWidget.class, 
 this));
   }


 The working prototype is fully functional, and passed the same test suites
 than GWT master. DevMode works fine, and I think SuperDevMode should work
 too.
 Please, feel free to add feedback in the document and/or GitHub. I
 apologize for my possible grammatical errors, since I'm not english native
 speaker.

 Links of interest:
 - Ray Cromwell's blog post:
 http://timepedia.blogspot.com.ar/2009/03/relaxing-constraints-on-gwtcreate.html
 - Rebinding Methods proposal:
 https://docs.google.com/document/d/1K25f6-Hxtlj31pthapfUhmNxS1OPiUXZFtHDnHGjrpg
 - Working prototype: https://github.com/andrestesti/gwt-rebindingmethods

 Thanks in advance.

 - Andrés Testi


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: Reminder: Branching GWT 2.6 later today

[Juan Pablo Gardella]

Thanks Mathew!


2013/11/5 Matthew Dempsky mdemp...@google.com

 In the mean time though, I think I successfully pushed 2.6.0-SNAPSHOT to
 https://oss.sonatype.org/content/repositories/google-snapshots/.


 On Tue, Nov 5, 2013 at 12:04 AM, Matthew Dempsky mdemp...@google.comwrote:

 As promised, I created the release/2.6 branch for tracking development
 towards 2.6.  At this point, development can continue on master towards the
 next release.  If you think a change should be made for 2.6, please propose
 it against master, and then notify me to cherry pick it onto release/2.6.

 Setting up the 2.6 release branch took longer than expected due to some
 last minute changes and technical issues.  I plan to finish preparing the
 2.6rc1 snapshot tomorrow morning, and push them out.  I'll send an
 announcement when that's ready.  Thanks for your patience and sorry for the
 slight delay.


 On Mon, Nov 4, 2013 at 1:58 PM, Matthew Dempsky mdemp...@google.comwrote:

 As a reminder, I'm going to create the GWT 2.6 branch later today and
 prepare a 2.6rc1 snapshot.  There's still some time to propose and submit
 patches, but it's down to hours remaining now.  Don't fret if you miss the
 deadline: there will be more releases in the future!



  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Google GWT team meeting notes for June 26th

[Juan Pablo Gardella]

Thanks for sharing!


2013/6/27 Brian Slesinsky skybr...@google.com

 Hi, in the interest of increased transparency, I'm going to start posting
 notes from GWT team meetings at Google. I'm not sure if we'll keep this up
 but we'll see how it goes.  (My apologies in advance for any errors.)

 June 26, 2013

 - Discussed goals for the next quarter. Of interest to the community:
 - Improving GWT compiler speed is important as usual.
 - Improve Super Dev Mode usability to improve internal adoption. In
 particular, figure out IDE integration.
 - Finish moving documentation to gwtproject.org and redirect from
 developers.google.com
 - Discussed what we should do with GWT designer documentation. The GWT
 designer is currently not being maintained. No resolution yet.
 - Discussed how to make mgwt available within Google.
 - Discussed community outreach, possibly by having public Hangouts and/or
 posting on YouTube. Still in progress. For now, Brian will write up meeting
 notes.
 - Gardening: new process seemed to work well. Matthew talked about
 automating it.
 - Talked about adding an end-to-end test for split points. Requires
 infrastructure.
 - Daniel: javadoc regenerated and moved to gwtproject.org to fix a
 security issue.
 - We discussed updating Google's internal widgets and widget architecture.
 Long term, one idea is to support web components written in JavaScript and
 come up with an improvement on JSNI and JavaScriptObjects to allow this.
 Goktug and Roberto have an idea they think will work. Short term unclear.
 Being able to consume GSS would help. Needs more discussion.

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

[gwt-contrib] GWT presentations

[Juan Pablo Gardella]

Hi all,

I saw presentations in the page are very old. How we can improve that?
http://www.gwtproject.org/presentations.html

Regards

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Re: GWT presentations

[Juan Pablo Gardella]

Thanks!


2013/5/28 Jens jens.nehlme...@gmail.com

 You can pull gwt-site from gwt.googlesource.com and then update


 https://gwt.googlesource.com/gwt-site/+/master/src/main/markdown/presentations.md

 Finally push your changes to Gerrit for review.

 http://www.gwtproject.org/makinggwtbetter.html#webpage

 -- J.

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---
 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.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Change in gwt[master]: removes block splitting logic that was specific to IE6/7

[Juan Pablo Gardella]

Please, don't remove IE7 support.


2013/4/18 Thomas Broyer t.bro...@gmail.com

 Thomas Broyer has posted comments on this change.

 Change subject: removes block splitting logic that was specific to IE6/7
 ..**..**..


 Patch Set 1: Code-Review-1

 If we start removing IE6/7 support, we should start with removing the ie6
 permutation, and only then (or at the same time) the supporting code.

 That said, IIRC, we settled on removing IE6/7 support after the 2.6
 release.

 --
 To view, visit 
 https://gwt-review.**googlesource.com/2550https://gwt-review.googlesource.com/2550
 To unsubscribe, visit 
 https://gwt-review.**googlesource.com/settingshttps://gwt-review.googlesource.com/settings

 Gerrit-MessageType: comment
 Gerrit-Change-Id: I620238c98f8385956d8df52b0d914**ad74e9011f5
 Gerrit-PatchSet: 1
 Gerrit-Project: gwt
 Gerrit-Branch: master
 Gerrit-Owner: John Stalcup stal...@google.com
 Gerrit-Reviewer: Thomas Broyer t.bro...@gmail.com
 Gerrit-HasComments: No

 --
 --
 http://groups.google.com/**group/Google-Web-Toolkit-**Contributorshttp://groups.google.com/group/Google-Web-Toolkit-Contributors
 ---You received this message because you are subscribed to the Google
 Groups Google Web Toolkit Contributors group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to 
 google-web-toolkit-**contributors+unsubscribe@**googlegroups.comgoogle-web-toolkit-contributors%2bunsubscr...@googlegroups.com
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
 .




-- 
-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [gwt-contrib] Any interest in having css3pie integrated with GWT?

[Juan Pablo Gardella]

+1

2011/9/28 Jeff Larsen larse...@gmail.com

 To be blunt, Trying to get styling to work right in IE is somewhat of a
 nightmare. Especially with the lack of css3 support.

 There is a library out there that fixes some of the major headaches
 css3pie. http://css3pie.com/
   border-radius,
 http://css3pie.com/documentation/supported-css3-features/#border-radius
 box-shadow,http://css3pie.com/documentation/supported-css3-features/#box-shadowborder-imagehttp://css3pie.com/documentation/supported-css3-features/#border-imageCSS3
  Backgrounds 
 (-pie-background)http://css3pie.com/documentation/supported-css3-features/#pie-background,
 Gradients,http://css3pie.com/documentation/supported-css3-features/#gradientsRGBA
  Color Valueshttp://css3pie.com/documentation/supported-css3-features/#rgba

 I've got a crude implementation up and running where it adds the necessary
 behavior :url('PIE.htc') and updates the background to use -pie-background
 when background : linear gradient is present. It relies on classpath
 placement to work properly, because I didn't want to go down the path of
 copy/pasting the whole ClientBundle architecture. Seriously gross and
 fragile.

 My question is, would this be something you'd be interestd in including in
 GWT proper with some sort of configuration to turn pie on or off? I think
 this would be something a lot of developers would be really happy to use and
 it then abstracts them away from changes to css3pie itself.

 Before commit, I'd get it so it would only push it to IE browsers, to help
 keep css files small for browsers that don't care about pie.
 Allow a config property in the gwt.xml file to override the included
 version of pie. The user would still be responsible for managing


 http://css3pie.com/documentation/supported-css3-features/#pie-watch-ancestors

 for the situations where that is warrented.


 I know this seems like a minor change, we're using pie to help us get our
 code out the door faster without having to sprite everything up. It is a
 HUGE productivity gain.  Having something that allows us to not have

 @if ie6 ie8 ie9 {
 .style1, style2, style3, style4{
behavior : url('PIE.htc')
 }
 }

 peppered throughout our code would sure be nice, and allow us to have one
 less thing to think about.

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] Activities Places

[Juan Pablo Gardella]

Thanks!!

2011/5/25 A. Stevko andy.ste...@gmail.com

 Thanks. I like it. It makes clearer some of the relationships.


 On Wed, May 25, 2011 at 11:43 AM, danieldietrich 
 cafeb...@googlemail.comwrote:

 Hi,

 I've drawn an informal map about Activities  Places
 - perhaps it is helpful for someone...

 Greetings from Kiel/Germany

 - Daniel

 (No warranty is given about correctness/completeness)

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors




 --
 -- A. Stevko
 ===
 If everything seems under control, you're just not going fast enough. M.
 Andretti





  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Re: [gwt-contrib] GwtEvent.setSource visibility

[Juan Pablo Gardella]

+1

2011/5/17 Ray Ryan rj...@google.com

 Yes please, we shouldn't have broken existing code like that.


 On Tue, May 17, 2011 at 3:25 PM, Stephen Haberman 
 stephen.haber...@gmail.com wrote:

 Hi,

 With the bindery package change, I have a custom EventBus implementation
 that no longer compiles. I was calling GwtEvent.setSource (and squatting
 in the c.g.g.e.shared package to do so), but now setSource is defined in
 the bindery package and so inaccessible.

 I can move my EventBus to the new bindery package and squat there, but
 it makes it complicated supporting both pre-2.4 and post-2.4 codebases.

 If possible, adding a GwtEvent.setSource that restored the old
 visibility would be preferable. I have a simple patch to do so if that's
 okay.

 At some point it would be nice to be able to implement an EventBus
 without squatting in a c.g package, though I understand the appeal of
 keeping the not for user code methods protected.

 - Stephen

 --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors


  --
 http://groups.google.com/group/Google-Web-Toolkit-Contributors


-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors