[
http://jira.codehaus.org/browse/MGWT-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Irvine updated MGWT-249:
------------------------------
Attachment: test.zip
test.zip is a very small test case. will add a comment that tells how to
duplicate the problem.
> archetype created project missing classpath entries
> ----------------------------------------------------
>
> Key: MGWT-249
> URL: http://jira.codehaus.org/browse/MGWT-249
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.1.x
> Environment: gwt 2.1
> eclipse helios
> gwt-maven-plugin 2.1.1-SNAPSHOT
> Reporter: Chuck Irvine
> Attachments: test.zip
>
>
> (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!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
