Hi,

I'm having a problem using WindowBuilder 1.2.0.r37 in the Google Eclipse
Plugin 2.4.2.relr37 with IvyDE 2.1.0 on Eclipse 3.7.1 that I've narrowed it
down to being the same as issues
5126<http://code.google.com/p/google-web-toolkit/issues/detail?id=5126>
and
6225 <http://code.google.com/p/google-web-toolkit/issues/detail?id=6225>.

These two issues generalise to making proper use of the classpath in
Eclipse, regardless of the source of the dependent jars (Ivy container,
Maven container, user library, jar in workspace, external jar, project
reference, etc.). Some of these dependency references work and some don't.
When they don't, WindowBuilder fails with cryptic error messages similar to
"WindowBuilder was unable to load <class name>. This may be caused by
ClassLoader problems."

Are there any plans to fix this? Issue
6365<http://code.google.com/p/google-web-toolkit/issues/detail?id=6365>,
that was fixed a couple of weeks ago, allows the plugin to look on the
project classpath for gwt-dev.jar. I would imagine that this is related to
the more general problem described in the two issues above, which have been
open since last July and this April, respectively.

Can anyone on the GPE team comment on this?

Many thanks,
Joe

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to