Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: 2.2.0
-
Fix Version/s: None
-
Labels:None
-
Environment:gwt 2.1
eclipse helios
gwt-maven-plugin 2.1.1-SNAPSHOT
-
Number of attachments :1
Description
(1) Created a project by invoking:
mvn archetype:generate -DarchetypeRepository=https://nexus.codehaus.org/content/groups/snapshots-group/ -DarchetypeGroupId=org.codehaus.mojo -DarchetypeArtifactId=gwt-maven-plugin -DarchetypeVersion=2.1.1-SNAPSHOT
(2) Imported as existing project into eclipse.
(3) Added new spring code and corresponding maven dependency.
(4) Invoked "Run as / Web Application"
At this point, the application is invoked in jetty but jetty reports that it finds the spring classes on the system class path, but not the web app classpath.
So, the issue is that the gwt eclipse plugin isn't picking up jar files in the maven library when running Jetty in the context described above.
Thanks!
-
Hide
- test.zip
- 03/Dec/10 10:05 AM
- 2.43 MB
- Chuck Irvine
-
- test/.classpath 1 kB
- test/.project 2 kB
- test/pom.xml 3 kB
- test/testTest-dev.launch 3 kB
- test/testTest-prod.launch 3 kB
- test/.settings/.jsdtscope 0.5 kB
- test/.../com.google.gdt.eclipse.core.prefs 0.1 kB
- test/.../com.google.gwt.eclipse.core.prefs 0.1 kB
- test/.../org.eclipse.jdt.core.prefs 0.4 kB
- test/.../org.eclipse.wst.common.component 0.6 kB
- test/.../org.eclipse.wst.common.project.facet.core.xml 0.2 kB
- test/.../org.eclipse.wst.jsdt.ui.superType.container 0.0 kB
- test/.../org.maven.ide.eclipse.prefs 0.3 kB
- test/src/.../client/GreetingService.java 0.4 kB
- test/src/main/.../example/client/test.java 5 kB
- test/src/.../server/GreetingServiceImpl.java 2 kB
- test/src/main/.../shared/FieldVerifier.java 2 kB
- test/src/main/.../example/test.gwt.xml 0.9 kB
- test/src/main/.../client/Messages.properties 0.0 kB
- test/src/.../client/Messages_fr.properties 0.0 kB
- test/src/main/webapp/test.css 0.6 kB
- test/src/main/webapp/test.html 3 kB
- test/src/.../clear.cache.gif 0.0 kB
- test/.../com.company.example.testJUnit.nocache.js 5 kB
- test/src/.../hosted.html 11 kB
- test/src/main/.../gwt/standard/standard.css 26 kB
- test/src/main/.../standard/standard_rtl.css 26 kB
- test/src/main/.../standard/images/corner.png 1 kB
- test/src/main/.../images/corner_ie6.png 0.4 kB
- test/src/main/.../images/hborder.png 1 kB
Activity
On your website at http://mojo.codehaus.org/gwt-maven-plugin/hosted.html, it is stated:
Google Eclipse plugin automatically handle launching the Hosted mode browser with a simple right click on your module gwt.xml file "run as > web application".
This is the operation that I have referring to, i.e. the operation generates the classpath related errors described previously.
something is missing in the documentation : we assume you use m2e
which doesn't look to be the case here.
is it the case ?
Hello Oliver (or anyone), any ideas on what is causing this problem? Thanks. I've tried everything that I can think of.
test.zip is a very small test case. will add a comment that tells how to duplicate the problem.
To duplicate problem:
(1) Import unzipped project by invoking "Import.../Existing Projects into Workspace.
(2) If you get any eclipse compile problems, invoke "Project / Clean"
(3) Start project with "Run as / Web Application"
(4) In Development Mode window, right click on url and invoke "open"
(5) When app comes up in browser window, click the "Send" button.
(6) Click "Close" button on pop up window.
(7) Look in the eclipse console window. You should see something like:
[WARN] Server class 'org.apache.commons.lang.StringUtils' could not be found in the web app, but was found on the system classpath
The problem is that the jar files of the maven dependencies are not getting added to the web app classpath. In the case above the problem isn't serious since the jar is found on the system classpath. However, in other cases where classes are dynamically loaded and only the web app class path is searched, the missing classes will cause serious application, i.e. class not found errors.
replace 1) with
1) Import unzipped project by invoking Import -> Maven Existing Maven Projects .
Will works better with using m2e for Import.
And again the issue here must concern the Gwt Maven Plugin !
We try to our best to have some compliants stuff for eclipse (m2e etc) but the main goal is to get things worked when invoking maven tru cli !
I miss you here with " gwt eclipse plugin" : what is that ??
AFAIK we support only maven builds.
So if gwt:run failed or anything related to maven I can help you.
But I cannot help you for eclipse issue