Re: [gwt-contrib] Re: user tests fail to compile

2014-06-15 Thread Thomas Broyer
On Sunday, June 15, 2014 3:07:17 AM UTC+2, Jens wrote: > > The gwt.javac macro in common.ant.xml excludes **/super/** by default, but >> the call point in compile.tests in user/build.xml overrides the excludes="" >> and removed the **/super/** exclusion. I think that was a bug (by >> oversight

Re: [gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread Jens
> > The gwt.javac macro in common.ant.xml excludes **/super/** by default, but > the call point in compile.tests in user/build.xml overrides the excludes="" > and removed the **/super/** exclusion. I think that was a bug (by > oversight). > Hmm I don't see anything that tells gwt.javac to excl

Re: [gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread Thomas Broyer
On Saturday, June 14, 2014 9:51:13 PM UTC+2, Jens wrote: > > I'm not sure why or when that happened. I checked in a big patch (#7600) >> recently that may or may not have caused it. I wonder if someone can seek >> back before my commit and see if the failure is still present. >> > > Its not you

Re: [gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread Jens
> > I'm not sure why or when that happened. I checked in a big patch (#7600) > recently that may or may not have caused it. I wonder if someone can seek > back before my commit and see if the failure is still present. > Its not your commit that caused these errors. The RequestFactory error si

Re: [gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread 'Ray Cromwell' via GWT Contributors
I'm not sure why or when that happened. I checked in a big patch (#7600) recently that may or may not have caused it. I wonder if someone can seek back before my commit and see if the failure is still present. On Sat, Jun 14, 2014 at 11:55 AM, Michael Prentice wrote: > I've uploaded a patch fo

[gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread Michael Prentice
I've uploaded a patch for this: https://gwt-review.googlesource.com/#/c/7890/3 On Saturday, June 14, 2014 10:22:47 AM UTC-4, Michael Prentice wrote: > > Thanks Jens, that worked great. > > This .classpath file is in source control, so this should probably go into > a patch. Is anyone working on

[gwt-contrib] Re: user tests fail to compile

2014-06-14 Thread Michael Prentice
Thanks Jens, that worked great. This .classpath file is in source control, so this should probably go into a patch. Is anyone working on one already? On Friday, June 13, 2014 4:28:29 AM UTC-4, Jens wrote: > > In Eclipse any folder that contains super source should be excluded from > the clas

[gwt-contrib] Re: user tests fail to compile

2014-06-13 Thread Jens
> > Eclipse still unhappy though of course. > In Eclipse any folder that contains super source should be excluded from the classpath so that its not treated as Java package but instead a simple folder with java files. So go to gwt-user project settings -> build path -> source. Select gwt-user/

[gwt-contrib] Re: user tests fail to compile

2014-06-12 Thread Michael Prentice
Full clean Ant build just finished and it passed with the build.xml tweak and the requestfactory-apt.jar update. Thanks Colin. Eclipse still unhappy though of course. Is there an issue/patch for this? Has anyone tracked down the original change set that caused this? I might be able to take a lo

[gwt-contrib] Re: user tests fail to compile

2014-06-12 Thread Michael Prentice
I hit the same thing last night. The fix you suggested may help with Ant, but it does not resolve the compile errors in Eclipse :( It doesn't look like Eclipse has any Annotations to ignore these types of severe errors either, I just pulled in the 4 commits from today and they don't help with t

[gwt-contrib] Re: user tests fail to compile

2014-06-12 Thread Colin Alworth
With some help from Jens Nehlmeier over in ##gwt, it looks like there are two distinct issues preventing the build from passing presently The first is that the class ImmediateCompileFails does in fact cause problems with compiling - the simplest fix was to tell the compile.tests target to leave