Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-11-14 Thread Brandon Donnelson
GPE uses gwt-codeserver.jar in the GWT_CONTAINER and it asks the user to add it to the classpath if it doesn't exist and super dev mode is on. I think idea uses the gwt-codeserver.jar in the runtime classpath but I haven't confirmed. On Friday, November 14, 2014 1:50:13 AM UTC-8, Thomas Broyer

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-11-14 Thread Thomas Broyer
So, what does the latest GPE do now? Can we revert the change and go back to what we had in 2.6 (and beta1) with SDM in its own gwt-codeserver.jar and *not* in gwt-dev.jar? (and what about IntelliJ IDEA? I must confess I haven't done any GWT dev –even bug repro checks– for a few weeks, and haven

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-11-02 Thread Brandon Donnelson
This is a bit tricker to deal with in the GPE source than I imagined. The current GPE patch is looking ready to go, but it validates checking for CodeServer in the classpath if SDM is turned on. Although it adds gwt-codeserver.jar to the GWT_CONTAINER resolved classpath. If the gwt-codeserver.

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-29 Thread 'Brian Slesinsky' via GWT Contributors
It looks like the gwt-codeserver jar will still exist, but the same classes will also be in gwt-dev.jar. So it's ugly but should be backward compatible? - Brian -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-29 Thread Thomas Broyer
On Tuesday, October 28, 2014 9:09:47 PM UTC+1, Brian Slesinsky wrote: > > Yes, merging the jars should be fine as a short-term fix. > Just though that it could break some plugins out there that would expect to find a gwt-codeserver 2.7.0 in Maven Central. For the gwt-maven-plugin, we release a ne

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-28 Thread 'Brian Slesinsky' via GWT Contributors
Yes, merging the jars should be fine as a short-term fix. Codeserver should be built as a separate library to enforce that there are no circular dependencies. (We already have one for DevMode -superDevMode but that should be fixed by splitting out DevMode; it doesn't belong in the same library as

Re: [gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-28 Thread 'Daniel Kurka' via GWT Contributors
I think moving sources right now is too risky and too much work we should just merge the jars in dist. On Tue, Oct 28, 2014 at 8:02 PM, Thomas Broyer wrote: > Fine for me. > > Do you intend to move the sources or just merge the JARs during > dist-dev/dist? > > -- > You received this message beca

[gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-28 Thread Thomas Broyer
Fine for me. Do you intend to move the sources or just merge the JARs during dist-dev/dist? -- 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-toolk

[gwt-contrib] Blocking RC1: Fold gwt-codeserver into gwt-dev

2014-10-28 Thread 'Daniel Kurka' via GWT Contributors
Hi all, right now GWT builds with RC1 are failing in Eclipse with GPE since the gwt-codeserver.jar is not on the build path. The next GPE release (with changes that fix this) is still a long way out. In order to not be blocking on this I propose we fold gwt-codeserver.jar into gwt-dev.jar. This w