On Friday, November 21, 2014 8:03:42 PM UTC+1, Thomas Broyer wrote:
I can't tell for App Engine, but why would you want a GWT SDK?
You're right, I was able to remove the GWT SDK plugin from Eclipse, and it
still works using the one from my maven repository.
That's not the case for GAE. If I
When you use Maven and Eclipse, you import a Maven project (ou create one
from within Eclipse), and the GPE detects the use of the gwt-maven-plugin
and auto-configures itself, using the GWT dependencies from your Maven
project rather than a GWT SDK (so you can really use any GWT version
that's
On Friday, November 21, 2014 11:33:48 AM UTC+1, Thomas Broyer wrote:
When you use Maven and Eclipse, you import a Maven project (ou create
one from within Eclipse), and the GPE detects the use of the
gwt-maven-plugin and auto-configures itself, using the GWT dependencies
from your Maven
On Friday, November 21, 2014 6:54:29 PM UTC+1, Phineas Gage wrote:
- You still want separate GWT and app engine SDKs installed in Eclipse,
even though you've also got them in your local maven repository.
I can't tell for App Engine, but why would you want a GWT SDK?
--
You received this
I'm in the process of Maven-izing my GWT 2.6.1 project (an intermediate
step to start using GWT 2.7.0), and as a first step want to switch to maven
style directory structure (as suggested by the Maven GWT Plugin
documentation
http://mojo.codehaus.org/gwt-maven-plugin/user-guide/project.html),
It sounds like you have non-gwt-capable classes in packages meant for GWT -
is that deliberate? For example, test classes to make sure the various
server components in your project work, but they are in your .client or
.shared package?
If they are not, then GWT will totally ignore them, as no
Sounds like a bug or misconfiguration of the GPE. Is the project a Maven
project in Eclipse? There might be some hard-coded paths in the GPE
(because of limitations of Eclipse) that are only triggered in one or the
other mode (Maven vs. simple Eclipse project). E.g. /test being
excluded from
On Thursday, November 20, 2014 8:47:35 PM UTC+1, Colin Alworth wrote:
It sounds like you have non-gwt-capable classes in packages meant for GWT
- is that deliberate? For example, test classes to make sure the various
server components in your project work, but they are in your .client or
On Friday, November 21, 2014 8:18:19 AM UTC+1, Thomas Broyer wrote:
Sounds like a bug or misconfiguration of the GPE. Is the project a Maven
project in Eclipse? There might be some hard-coded paths in the GPE
(because of limitations of Eclipse) that are only triggered in one or the
other
