Thanks Jason! That sounds like a reasonable workaround. On Mon, Aug 31, 2009 at 10:50 AM, Jason Parekh <jasonpar...@gmail.com>wrote:
> Hi Jack, > This is a known issue. > > For jars referenced by your dependent projects, the typical workaround is > what you've described. > > For the source in your dependent projects, you could add linked source > resources in your main project pointing to the dependent projects' source > directories. > > jason > > > On Sun, Aug 30, 2009 at 12:19 AM, jack <jack.terran...@gmail.com> wrote: > >> >> I have a simple GWT project in Eclipse that requires another external >> project. Everything builds fine. But when I launch as a Google Web >> App using the App Engine I get a server-side NoClassDefFound for >> classes located in the external project. >> >> I've played around with the launch config and can't get around this. >> Under the classpath tab when I select the external project, Eclipse >> also chooses the project's dependent jars, but when I run the GWT >> project apparently Eclipse is not making these jars available to the >> App Engine. >> >> I can jar up the external project and cram it into WEB-INF/lib of my >> GWT project - the error goes away then. But this requires me to >> gather up every jar that the external project relies on and place it >> under WEB-INF/lib. I imagine Eclipse should be doing this for me >> through the launch configuration. >> >> Thanks in advance >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
