2.8.0 RC1 is here!

['Daniel Kurka' via GWT Users]

Hi all,

I just build the GWT 2.8.0 RC1 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble. You can 
either reply to this thread on gwt-contrib 

 or file bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC1 

 
will be made available shortly after this notice, in the mean time you can 
take a look at the github repository 

.

Daniel,
on behalf of the GWT team

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.8.0 RC1 is here!

['Daniel Kurka' via GWT Contributors]

Hi all,

I just build the GWT 2.8.0 RC1 and pushed it to maven central. The complete 
SDK is also available from here .

Please start testing and let us know if you run into any trouble and file 
bugs .

We are planing to release this as GWT 2.8.0 if we do not here about any 
serious issues within the next two weeks. The release notes for RC1 

 will 
be made available shortly after this notice, in the mean time you can take 
a look at the github repository 

.

Daniel,
on behalf of the GWT team

-- 
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/3448c7da-f600-48a6-90c4-08172f841283%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using custom servlet for GWT-RPC with GWTTestCase

[Kay Pac]

This worked great for a while, but I think it broke at some point. I just 
don't know when it stopped working. I'm sure it is something on my end or 
in my code. But my  element is no longer working. I've checked the 
jetty debug logging and the paths are matching, but jetty is still 
directing my requests to the default servlet.

I will continue to investigate, but for some reason I can't access my 
servlet in the tests.

Kay

On Sunday, November 23, 2014 at 3:13:11 PM UTC-8, Thomas Broyer wrote:
>
> For tests with JUnitShell, the servlets have to be declared in the 
> .gwt.XML file with a  element.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Thinking about the future: GWT 3, J2Cl, modularization, etc.

[Thomas Broyer]

Hi all,

We've talked about modularizing GWT for several years now, and I gave it a
try at several occasions, with Maven, then Gradle, then Buck… and last year
I completely gave up, knowing the J2Cl was coming which would be quite
disruptive, with the hope that we could start on new grounds (including a
fresh start from the built tool side; farewell Ant!). As GWT 2.8.0 is
approaching (RC1 is imminent), I think it's time we start talking about
that GWT 3 future with J2Cl at its core.

As I understand it, Google would rather have things as "exploded" as
possible: J2Cl and emulation in one repo (or possibly even split in 2),
then each "module" in its own repo (elemental2, etc.) with its own
maintainers and moving at its own pace (and possibly even its own
contributing guidelines: using GitHub+Travis? Gerrit+Jenkins?
GitHub+GerritHub+Travis? and its own build tools: Maven vs. Gradle vs.
whatever)
First: I'm all for it!
The way I see it, Google would opensource J2Cl, and we (the community)
would start moving bits from GWT out to their own repos (either removing
them from GWT proper –the challenge then is to make sure it stays
compatible with both GWT 2.x and J2Cl/GWT 3.x– or duplicating them –the
challenge being to keep both versions in sync, as we don't want to abandon
GWT 2.8.x users; but 2.x maintenance is another, though closely related,
topic).

It's been suggested during the last Steering Committee meeting that the
community (i.e. "outside Google") may want to package/bundle many such
things together into "GWT 3.x" releases; probably a bit similar to how
Eclipse cuts yearly releases bundling many plugins/features together into
downloadable packages.
On one hand, it requires picking (or cutting?) specific "releases" of each
module to be bundled and testing them all together to make sure they all
play well with each other, which is relatively time-consuming (and one
reason Google doesn't want to do it, given they don't even use "releases"
internally but always run "from trunk").
On the other hand, it makes it easy for users, particularly newcomers, to
refer to their setup: “I use GWT 3.0.1” vs. “I use J2Cl x, emul y,
elemental2 z, polymer-jsinterop i, places j, activities k, etc.”
Also, without such bundles, what it is that we would call “GWT 3”? Would it
become an “umbrella term” a bit like “HTML5”?

There's also been pushbacks from the community that we should have
(possibly semi-automated) releases several times a year (every month, every
quarter, or twice a year), even with minimal testing (not as "unstable" as
"nightlies" –which we currently have with SNAPSHOTs– but more similar to a
"canary" release channel).
That being said, if we use a "rather standard" build tool (Gradle?), people
could use JitPack to "pin" a specific commit/snapshot without the need to
have formal intermediate releases (with jitpack.yml one could probably
build using Bazel or Buck too, after wget'ing them).

So, WDYT? What should “GWT 3” look like? one bundle like today or a set of
projects? or possibly a set of projects with a scaffolding tool (yeoman?)
and build tool integrations?
Also, what would gwtproject.org say? would it talk about each module? or
leave each module's documentation to the modules themselves? (note that we
could come up with a rule saying that each maintainer is responsible for
updating the documentation on gwtproject.org, with someone to "unlist"
projects that don't comply for too long). Would GWT 3 become an "ecosystem"
around J2Cl more than a "project" by itself? (note that there are branding
–i.e. legal– issues too around that).

I, for one, would be OK with just "a set of projects" on a "practical"
basis, though I easily admit that it probably wouldn't help "marketing" it.

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

Re: [gwt-contrib] Re: Experimental release of Elemental2

[Steve Andrews]

I've done some more testing and cleared my cache and can still only get 
EventListener to work with the generateJsInteropExports flag set.

I've had another problem with EventListener on a select element but I'm 
using an external framework for my project (Materialize) and think that 
it's their framework that doesn't like the EventListener object. If I use a 
standard select element then it's working. I can get around this by adding 
the listener through a JQuery wrapper so no problem.

I've also found that Window.location returns an Object - will this be 
sorted in a future release?

Other than that Elemental is working well so far! Nice work!

Steve

On Friday, 22 July 2016 11:31:24 UTC+1, Jens wrote:
>
>
> It only works with the generateJsInteropExports flag set though.
>>
>
> Sounds like a bug to me.
>
> -- 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/16498b97-7d3d-44c7-b42b-e40be9de1e26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.