I sometimes, when I'm a bit desperate, I debug the project, find some
classes for the conflicting code using the
"Thread.currentThread().getContextClassLoader().loadClass(...)", and use
the variable inspector to find the class loader and the actual file that
has been used to load the class.
We have seen similar issues with this when we were experimenting with some
projects and upgrading to 2.8.2. The things to double check are:
1. That there are no duplicate jars from different versions of GWT, as
mentions by Thomas Broyer.
2. Delete any GWT generated folder such as the
That could definitely be the issue. Unfortunately, when we move back to a
previous version of the project we still get the same error so we think it
might be something with the eclipse environment and are going to try a new
eclipse install.
On Monday, May 14, 2018 at 12:34:20 PM UTC-4, Thomas
Could one of your dependencies possibly "shadow" its own version of
ImageResourceGenerator that had been compiled against GWT 2.8? You'd have
to revert to an older version of that dependency then.
On Monday, May 14, 2018 at 3:37:34 PM UTC+2, Rachel wrote:
>
> Thank you for responding. I'm
Thank you for responding. I'm looking at the build path and both gwt-user
and gwt-dev jar files are from 2.7. Is there somewhere else I should look?
On Monday, May 14, 2018 at 9:16:18 AM UTC-4, Thomas Broyer wrote:
>
>
>
> On Monday, May 14, 2018 at 3:06:09 PM UTC+2, Rachel wrote:
>>
>> We have
On Monday, May 14, 2018 at 3:06:09 PM UTC+2, Rachel wrote:
>
> We have to move our project back to GWT 2.7 due to some java 1.8 issues.
> I've checked all my jar files to make sure they are 2.7 and no duplicate
> jars in the build path but am getting errors when I try to compile with Ant.
>
