GXT 2.2.0 and GWT Eclipse plugin - Errors when validating newly compiled units

[ygrenzinger]

Hello,

I use GWT plugin from Google in hosted mode.
With GXT 2.1.1 no problem.

But with GXT 2.2.0 just released I have lots of error when displaying the page :
17:07:47.518 [DEBUG] [com.cie1818.ariane.ihm.Ariane] Validating newly compiled units
17:07:47.518 [ERROR] [com.cie1818.ariane.ihm.Ariane] Errors in 'jar:file:/D:/dev/sources/Ariane/trunk/ArianeIhmGXT/src/main/webapp/WEB-INF/lib/gxt.jar!/com/extjs/gxt/ui/client/aria/ToolBarHandler.java'
17:07:47.533 [ERROR] [com.cie1818.ariane.ihm.Ariane] Line 36: The method firstActive(PagingToolBar) is undefined for the type ToolBarHandler
etc etc

17:07:48.002 [ERROR] [com.cie1818.ariane.ihm.Ariane] Errors in 'jar:file:/D:/dev/sources/Ariane/trunk/ArianeIhmGXT/src/main/webapp/WEB-INF/lib/gxt.jar!/com/extjs/gxt/ui/client/widget/grid/filters/Filter.java'
17:07:48.018 [ERROR] [com.cie1818.ariane.ihm.Ariane] Line 119: Events.Serialize cannot be resolved
etc etc

There is number of "errors" like this.
However the application seems to work fine.

Any tips where it could come from ?

Thanks,
Yannick

[sven]

Are you sure that you updated the gxt.jar everywhere you reference it?

[ygrenzinger]

"Are you sure that you updated the gxt.jar everywhere you reference it? "

Really sure (dependancy managed by maven)
I'm using gwt 2.0.3 and Eclipse 3.5

[sven]

Well, there error could indicate that you havent. Events.Serialize is there in the Events class. So an error that it cannot find the event could be that you are using an old gxt.jar somewhere, that does not ahve this event.

Also you are using maven, i would really doublecheck this. Never trust a system to be perfect. You can also try to clean your workspace.

[pullo]

check for other gxt*.jars in your eclipse classpath. I had the same error. I had gxt.jar (2.1.1) and gxt-2.2.1.jar in my classpath ( in eclipse , go to debug configuration , classpath tab). removing gxt.jar solved the problem.
gxt.jar (2.1.1) contains some of the same classes as gxt-2.2.1.jar , but with different access specifiers for the methods. for me the classes in gxt.jar were getting loaded and not the classes on gxt2.2.1, and hence this issue.
-pullo