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.jar stays int the gwt-sdk moving forward this isn't an issue, although, if it doesn't the consistency between 2.5 to 2.7 will be different. This creates a challenge with testing in GPE because now that I've added validation, I have to change the unit tests around and it only has one GWT_ROOT, based on the latest sdk, which means the older SDK would need gwt-codeserver.jar and the newer won't.
I think GPE plugin update could release first of next week, this could fix the need to fold it into gwt-dev and keep things simpler as it is now. I think I'm going to hold off on the GPE fold into gwt-dev changes until next week and see how the release looks. Brandon On Wednesday, October 29, 2014 9:35:14 AM UTC-7, Brian Slesinsky wrote: > > 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 and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/119b59a7-bd06-4395-9300-00a970dfb07a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
