GWT error detection screwed up in 7255?

I am trying build 7255 (I was previously on 7241) and it seems that the gwt plugin has some serious problem recognizing errors: every class imported from an external module is marked red with a tooltip stating something like:

"class 'com.google.etcetc' is defined in module 'com.google.etcetc.' which is not inherited in module 'it.pip.etcetc.".

Needless to say that every error is wrongly detected.

Am I the only one seeing this? (well, actually it's happening to the two of us who upgraded, but it may be something in our project...).

3 comments
Comment actions Permalink

Hello Davide,

Please press Ctrl+B on the highlighed reference and check whether the referenced
class located in gwt-user.jar of your GWT installation.

I am trying build 7255 (I was previously on 7241) and it seems that
the gwt plugin has some serious problem recognizing errors: every
class imported from an external module is marked red with a tooltip
stating something like:

"class 'com.google.etcetc' is defined in module 'com.google.etcetc.'
which is not inherited in module 'it.pip.etcetc.".

Needless to say that every error is wrongly detected.

Am I the only one seeing this? (well, actually it's happening to the
two of us who upgraded, but it may be something in our project...).



0
Comment actions Permalink

Please press Ctrl+B on the highlighed reference and
check whether the referenced
class located in gwt-user.jar of your GWT
installation.


Gosh, you're right. I had a library defined from a gwt-user.jar in a different dir (although it was the same version). Now I also understand the fix saying that I had no gwt-user.jar in my module. But how comes this has only appeared after the upgrade??

Note that when I accepted the fix, the gwt-user lib was added to the module but since I had another library defining the same jar there was no effect. May I suggest that the intention/quick fix report the fact that jar from a different location is used?

0
Comment actions Permalink

Hello Davide,

>> Please press Ctrl+B on the highlighed reference and
>> check whether the referenced
>> class located in gwt-user.jar of your GWT
>> installation.

Gosh, you're right. I had a library defined from a gwt-user.jar in a
different dir (although it was the same version). Now I also
understand the fix saying that I had no gwt-user.jar in my module. But
how comes this has only appeared after the upgrade??


This feature has been implemented not long ago (IDEADEV-11532).

Note that when I accepted the fix, the gwt-user lib was added to the
module but since I had another library defining the same jar there was
no effect. May I suggest that the intention/quick fix report the fact
that jar from a different location is used?

Yes.


0

Please sign in to leave a comment.