[gwt-contrib] Github issue tracker label cleanup

I noticed that the Github issue tracker has a large number of labels and IMHO most of them are not used anymore. If time permits I thought about cleaning labels up so its more streamlined: - Convert Milestone labels to Github Milestones - Adjust category labels to match

Re: [gwt-contrib] Re: Compiler failing with java 7

It is true that GIN is kind of unmaintained. There has been some internal patches but nobody bothered moving the project out of Google code and export those due to initial overhead. Bu regardless, right now GIN uses reflection with a ClassLoader hack to access types. And at least some code

Re: [gwt-contrib] Re: Compiler failing with java 7

That's fair. I wasn't expecting much need either but just wanted a simpler way out if it ended up being important for the community. On Wed, Feb 17, 2016 at 11:57 PM, Manuel Carrasco Moñino wrote: > I follow, but I have a couple of thoughts > > - Is it actually useful from

Re: [gwt-contrib] Re: Compiler failing with java 7

On Thursday, February 18, 2016 at 6:29:22 PM UTC+1, Jens wrote: > > > Isn't GIN unmaintained anyway? >> > (and what we're all waiting for is proper GWT support in Dagger 2 ;-) ) >> > > I don't know. GIN works well and a ton of apps use it. > Well, at least it's not actively developed: with

Re: [gwt-contrib] Re: Compiler failing with java 7

On Wednesday, February 17, 2016 at 9:13:43 PM UTC+1, Goktug Gokdogan wrote: > > I think you didn't understand what I said. Let me try to clarify: > > "For any reason, if community wants to run the GWT 2.8 SDK in Java 7 > source level *(i.e. gwtc sourcelevel 7)*, they can theoretically do it by

Re: [gwt-contrib] Re: Compiler failing with java 7

> Isn't GIN unmaintained anyway? > (and what we're all waiting for is proper GWT support in Dagger 2 ;-) ) > I don't know. GIN works well and a ton of apps use it. A lot of these apps will probably not migrate to Dagger 2 anytime soon (especially not if it takes ages for a PR to be

Re: [gwt-contrib] Re: Compiler failing with java 7

Isn't GIN unmaintained anyway? (and what we're all waiting for is proper GWT support in Dagger 2 ;-) ) On Thursday, February 18, 2016 at 1:20:34 PM UTC+1, Jens wrote: > > Seems like GWT apps that use GIN will still require Java 8. I just tried > latest master from today using Guava 20-SNAPSHOT,

Re: [gwt-contrib] Re: Compiler failing with java 7

Agree, there are some corner cases, but normally gwt developers have to deal with a bunch of differences between java and gwt. Anyway I think that it's better that SDK7 users assume some language issues than not be able to compile their projects at all. On Thu, Feb 18, 2016 at 10:17 AM, 'Daniel

Re: [gwt-contrib] Re: Compiler failing with java 7

We have seen issues internally where some code would be a compile error in Java8 but not in Java7 (especially around type checking). This setup will leave users vulnerable to this since their code will compile in their IDE, but will fail GWT compile. On Thu, Feb 18, 2016 at 8:57 AM Manuel