It was in the main navigation panel. But as of this morning (GMT+1) it
works fine. So I guess it had something to do with caching ?
On Wed, Jun 11, 2014 at 6:01 PM, Thomas Broyer t.bro...@gmail.com wrote:
Hmm, which link? (on which page)
(there used to be such a bug, but it was fixed a few
I’m trying to bring https://gwt-review.googlesource.com/#/c/3361/ up to
date, and after rebasing and fixing a few whitespace nits I tried to run
the tests by they failed. Concerned that I had broken something I backed
off to current master, and ran tests again. First I did a clean dist-dev in
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
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
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
