Which plug-in do you use?
On Fri, Dec 11, 2009 at 1:49 PM, Graham graham.mor...@gmail.com wrote:
I've successfully upgraded to GWT 2.0 using the GWT Eclipse Plugin.
All seems well, with one exception. I write all of my servlets in a
seperate project, which worked under well under 1.* by
Google Plugin for Eclipse 3.5, version 1.2.v200912062003 running
Google Web Toolkit SDK 2.0.0.v2000912062003
On Dec 29, 1:11 pm, Murat Doner murat.do...@obss.com.tr wrote:
Which plug-in do you use?
On Fri, Dec 11, 2009 at 1:49 PM, Graham graham.mor...@gmail.com wrote:
I've successfully
I have the situation where the POJOs which are used within the
EntryPoint (i.e. compiled to Javascript) are located in another
Eclipse project.
If I configure the GWT project to refer to the other project the Java
compiles okay, but when attempting to compile to Javascript it
complains No source
Hi
The java *source* folder must be added to the classpath.
HIH
On Tue, Dec 29, 2009 at 1:09 PM, Matt matt.seab...@gmail.com wrote:
I have the situation where the POJOs which are used within the
EntryPoint (i.e. compiled to Javascript) are located in another
Eclipse project.
If I configure
Is there a specific way to do this?
Using the GWT projetct's 'Properties' dialog I removed the referenced
project from the 'Projects' tab and added the class folder in the
'Libraries' tab, then identified its source folder.
I can navigate to the source via the 'Referenced Libraries' of the GWT
I've successfully upgraded to GWT 2.0 using the GWT Eclipse Plugin.
All seems well, with one exception. I write all of my servlets in a
seperate project, which worked under well under 1.* by simply adding
the project to the build path.
Unfortunately after moving to GWT 2.0 the project is being
Sorry, just to clarify - I am referring specifically to development
mode.
On Dec 11, 11:49 am, Graham graham.mor...@gmail.com wrote:
I've successfully upgraded to GWT 2.0 using the GWT Eclipse Plugin.
All seems well, with one exception. I write all of my servlets in a
seperate project, which
This seems to be related to the AppEngine, which I don't need. Problem
solved!
On Dec 11, 11:51 am, Graham graham.mor...@gmail.com wrote:
Sorry, just to clarify - I am referring specifically to development
mode.
On Dec 11, 11:49 am, Graham graham.mor...@gmail.com wrote:
I've successfully
This is a general problem with having your GWT or App Engine project depend
on another project that ultimately contributes artifacts to the
war/WEB-INF/lib folder. We're going to address this in a future version of
the plugin.
Even though this appears to work in GWT, you'll still have to revert
