If everything is static pages, what about firebase?
--
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
Thanks Thomas. As always you pointed me in the right direction. I've got a
dependency to com.gwtplatform::gwtp-all which depends
on javax.servlet::servlet-api::2.5. Adding an fixes this and
SuperDevMode is running again!
Am Freitag, 29. Juli 2016 18:06:04 UTC+2 schrieb Thomas Broyer:
>
>
Check your dependencies, you may have Servlets API pre-3.0 (which
introduced this method); either coming before Servlets API 3.1 in the
classpath (they don't have the same artifactId so they could both be
present), or in place of 3.1 (if javax.servlet:javax.servlet-api is somehow
excluded).
Running SuperDevMode using GWT 2.8.0-rc1 and the GWT Maven Plugin from
Thomas (net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-6:devmode) throws an
exception. Not sure whether it's related to RC1 or the maven plugin.
[INFO] The code server is ready at http://127.0.0.1:9876/
[WARNING] Exception in
No, this is another issue; once you updated to Java 8, but still due to the
custom classloader.
On Friday, July 29, 2016 at 4:37:12 PM UTC+2, Frank Hossfeld wrote:
>
> Does using the compiler flag:
>
> -setProperty gin.classloading.exceptedPackages=com.google.gwt.core.client,
>
I'd start with double-checking your dependencies. With 2.8 from the Central
repository, most dependencies that used to be bundled into the gwt-user and
gwt-dev JARs have now been unbundled and properly declared as Maven
dependencies, so you may have had exclusions that now need to be removed.
I
It resolved the compilation problem, but it did throw something like a
javascript error "cannot resolve property gwidgets of undefined" which I
could not resolve, even by adding namespaces.
Le mercredi 27 juillet 2016 16:42:12 UTC+2, Jens a écrit :
>
>
> Thanks for your suggestion. SNAPHOT
Seems like gwt-dev is not in your classpath
El vie., 29 jul. 2016 a las 16:27, Frank Taffelt (<
frank.taff...@interface-projects.de>) escribió:
> thanks for the rc.
>
> updated a project coming from 2.7.0. the project is mainly based on thomas
> gwt maven-archetypes.
>
> the following build
Does using the compiler flag:
-setProperty gin.classloading.exceptedPackages=com.google.gwt.core.client,
com.google.gwt.core.client.impl
as mentioned in the workaround solve this issue.
Am Freitag, 29. Juli 2016 16:26:14 UTC+2 schrieb Thomas Broyer:
>
>
>
> On Friday, July 29, 2016 at
thanks for the rc.
updated a project coming from 2.7.0. the project is mainly based on thomas
gwt maven-archetypes.
the following build error is dumped doing an mvn package on the
gwt-compilation step:
[INFO] [WARN] Line 39 column 7: encountered "(". Was
expecting one of:
On Friday, July 29, 2016 at 1:41:33 PM UTC+2, kimi wrote:
>
> ok, didn"t know gin work with jdk7, just saw this in the release note :
> https://github.com/gwtproject/gwt/issues/9311
> i'm on jdk7, guava18 and gin 2.
>
The thing with GIN is that it uses a custom ClassLoader to be able to
"read"
On Friday, July 29, 2016 at 2:49:17 PM UTC+2, Andreas Ofner wrote:
>
> Hi Manuel,
>
> Am Freitag, 29. Juli 2016 13:47:43 UTC+2 schrieb Manuel Carrasco Moñino:
>>
>> About github pages with custom domains, the only minor I see is that it
>> does not supports https, but currently our site is not
Hi Manuel,
Am Freitag, 29. Juli 2016 13:47:43 UTC+2 schrieb Manuel Carrasco Moñino:
>
> About github pages with custom domains, the only minor I see is that it
> does not supports https, but currently our site is not https enabled, so
> not a big deal in the short time.
>
GitHub recently
> ok, didn"t know gin work with jdk7, just saw this in the release note :
> https://github.com/gwtproject/gwt/issues/9311
> i'm on jdk7, guava18 and gin 2.
>
Then Guava 18 is most likely blocking you, and you would need to use Guava
20 SNAPSHOT. Guava 18/19 use some private GWT API that does
Sound really good for us! Also similar to JEE which sync a group of
libraries and freezes its version in each releases. The idea of 2.9 to be
the modular release without J2CL involved sound good too!
I have been thinking in two ideas that might reduces the release and
marketing problem
Since 3.0 details aren't yet clear enough, I agree that it should be
modular, and eventually modules from 2.8.x could be used or ported to 3.0
So the ideal situation is that we are able to split gwt 2.8.x into as much
independent modules as possible, making GWT easier to maintain, and assign
Very nice indeed!
Now I'm just waiting for App Engine to support Java 8, then I can start
migrating our codebase, hurray!
Thanks!
On Friday, July 29, 2016 at 7:39:39 AM UTC+2, Daniel Kurka wrote:
>
> Hi all,
>
> I just build the GWT 2.8.0 RC1 and pushed it to maven central. The
> complete SDK
About github pages with custom domains, the only minor I see is that it
does not supports https, but currently our site is not https enabled, so
not a big deal in the short time.
El vie., 29 jul. 2016 a las 13:36, Manuel Carrasco Moñino (<
man...@apache.org>) escribió:
> Nothing special, it
ok, didn"t know gin work with jdk7, just saw this in the release note :
https://github.com/gwtproject/gwt/issues/9311
i'm on jdk7, guava18 and gin 2.
On Fri, Jul 29, 2016 at 12:20 PM, Thomas Broyer wrote:
>
>
> On Friday, July 29, 2016 at 12:16:30 PM UTC+2, Juan Pablo
Nothing special, it gets the resource based in the pathinfo, decode it to
utf-8, computes the content-type based on the extension, and writes the
answer to the client.
It is not storing any info in database, because we use google analytics for
counting visits. The GA script is statically included
Hi Kirill, this is a known limitation of the mojo plugin, you really should
try this one https://github.com/tbroyer/gwt-maven-plugin/ which solves most
of the limitation of the mojo plugin. In any case, mojo plugin will be
released as 2.8.0-rc1 in the next days.
On Friday, July 29, 2016 at
Why don't we use Github pages with custom domain? Never looked into the
code, does the servlet anything special?
-- 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
On Friday, July 29, 2016 at 12:16:30 PM UTC+2, Juan Pablo Gardella wrote:
>
> You could replace it with dagger2.
>
+1
Easier said than done though. For example, we have a lot of factories, and
moving them to AutoFactory is not straightforward either (we have many
factories able to provide
Hello all.
Due to changes in the GAE java Remote API, the uploader tool that we have
to update the gwtproject.org site is not working anymore.
Julien has updated last changes by hand (thanks Julien), but this is a
tough task and we should fix the issue.
Although I can take the time to fix the
On Friday, July 29, 2016 at 11:23:41 AM UTC+2, kimi wrote:
>
> nice, thanx for the great work.
>
> the only blocking point for me now is GIN.
>
GIN or Java 7? Because GIN with Java 8 works (in our project I didn't even
need the workaround)
No, what's blocking many of use is currently Guava
You could replace it with dagger2.
On Fri, 29 Jul 2016 at 06:51 Jens wrote:
>
> the only blocking point for me now is GIN.
>>
>
> Why its blocking?
>
> -- J.
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To
The release note is now available on the web site:
http://www.gwtproject.org/release-notes.html#Release_Notes_2_8_0_RC1
- Julien
On Fri, Jul 29, 2016 at 11:19 AM Jens wrote:
> You should file a bug on the maven plugin issue tracker
>
> the only blocking point for me now is GIN.
>
Why its blocking?
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
nice, thanx for the great work.
the only blocking point for me now is GIN.
On Fri, Jul 29, 2016 at 7:40 AM, 'Daniel Kurka' via GWT Users <
google-web-toolkit@googlegroups.com> wrote:
> Hi all,
>
> I just build the GWT 2.8.0 RC1 and pushed it to maven central. The
> complete SDK is also
You should file a bug on the maven plugin issue tracker
https://github.com/gwt-maven-plugin/gwt-maven-plugin
-- 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
Hi Daniel,
Thanks for the release.
The maven plugin still requires (and downloads) the BETA version, even if
my project does not have BETA in configuration.
There is a workaround, Thomas kindly pointed to it, but.
Is it possible to update the plugin ?
Thanks
On Friday, July 29, 2016 at
My IDEA works perfectly with GWT master.
On Friday, July 29, 2016 at 9:17:05 AM UTC+3, Kay Pac wrote:
>
> That is fantastic! Thanks to you and the rest of the team for your hard
> work. I am having trouble with IDE support, but that is related to the
> product (IntellIJ) and not GWT itself
>
>
It's working for me in IntelliJ Ultimate. The community edition does not
support the GWT.
On Friday, 29 July 2016 11:47:05 UTC+5:30, Kay Pac wrote:
>
> That is fantastic! Thanks to you and the rest of the team for your hard
> work. I am having trouble with IDE support, but that is related to
That is fantastic! Thanks to you and the rest of the team for your hard
work. I am having trouble with IDE support, but that is related to the
product (IntellIJ) and not GWT itself
Awesome!
On Thursday, July 28, 2016 at 10:39:39 PM UTC-7, Daniel Kurka wrote:
>
> Hi all,
>
> I just build the
34 matches
Mail list logo