No, you can't do that. Why is creating one tiny XML file a problem?
On Mon, Jun 8, 2009 at 9:06 PM, Scott sc...@selikoff.net wrote:
No one knows how to allow a GWT project to access a plain java project
in eclipse without turning it into a GWT module?
On Jun 3, 5:24 pm, Scott
Well from a design perspective, its not really a simple, stand-alone
library project if the entire thing is dependent on GWT. Second, as I
discovered when I tried it out, it also has to be framed with a GWT
package structure. in other words, files had to be placed in sub-
packages such as
Well from a design perspective, its not really a simple, stand-alone
library project if the entire thing is dependent on GWT.
What makes the entire thing dependent on GWT?
Second, as I
discovered when I tried it out, it also has to be framed with a GWT
package structure. in other words,
No one knows how to allow a GWT project to access a plain java project
in eclipse without turning it into a GWT module?
On Jun 3, 5:24 pm, Scott sc...@selikoff.net wrote:
Does that mean the shared library has to be a module? I'd prefer to
keep the shared library a simple Java project with no
I have code a set of Java POJOs within my project that are used to
transfer information around the application. I'd like to move them
into a simple Eclipse project so that they may be used by other
components. When I create a new Java project and move the POJOs to
this project, I add the new
In your .gwt.xml, you need one entry to specify a module like
inherits name=”logical-module-name“/. In the module, there is a
source code folder like source path=”path“/.
Jim
http://www.gwtorm.com - GWT ORM
http://code.google.com/p/dreamsource-orm/
On Jun 3, 1:27 pm, Scott sc...@selikoff.net
Does that mean the shared library has to be a module? I'd prefer to
keep the shared library a simple Java project with no dependencies on
libraries and only containing POJOs.
On Jun 3, 12:26 pm, Jim jim.p...@gmail.com wrote:
In your .gwt.xml, you need one entry to specify a module like
