Hi,
Thanks for this, really happy to have it around.
We were using 2.8.0-beta1 version for a while without any major fuss.
While upgrading to 2.8.0 released version, we get stuck with codeserver
refused to start because of class loading issues.
Here are the changes which we had to made.
x
I just sent the announcement to gwt-users that its now final, the reason
you could see the tag is that I pushed this as part of our release process.
The reason the tag is 17 days old is that its identical with that commit
(we have not changed GWT), traditionally we just turn the RC into the final
Make sense ... good to have the 2.8 ready now! :-)
--
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.c
On Friday, October 21, 2016 at 1:43:14 PM UTC+2, Lars wrote:
>
> Github show is a (final) 2.8 release (17 days ago)
> https://github.com/gwtproject/gwt/releases/tag/2.8.0
> Why is nobody talking about?
Waiting for release notes and a few documentation updates before making an
official announc
Hi,
Maven plugin isn't there:
https://mvnrepository.com/artifact/org.codehaus.mojo/gwt-maven-plugin
Has anyone know what is needed to trigger maven plugin ?
Thanks
On Friday, October 21, 2016 at 2:29:54 PM UTC+2, Jens wrote:
>
> The release is 2 days old (yes it's already on maven central) an
The release is 2 days old (yes it's already on maven central) and will
likely be announced once release notes are merged and uploaded.
Github just says it's 17 days ago because the commit that has been tagged
is 17 days old.
-- J.
--
You received this message because you are subscribed to th
