[ 
http://jira.codehaus.org/browse/MGWT-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241662#action_241662
 ] 

jieryn commented on MGWT-226:
-----------------------------

I should have given more details. In order to exploit, unpack the zip file and 
then:

{code}cd MGWT-226
mvn install
cd gwt
mvn gwt:run
{code}

You can use the -Pgood to enable the good version of the gwt-m-p which was last 
working in r12281 which you will need to install locally. With the working 
version, the two buttons will perform GWT-RPC calls and return hello and 
goodbye strings, respectively. With the bad version, which was installed 
locally via r12957 (HEAD), these services fail with 404 because the rpc1 and 
rpc2 module jars are not in the classpath for the embedded development mode 
server.

> Regression: Classpath no longer established properly
> ----------------------------------------------------
>
>                 Key: MGWT-226
>                 URL: http://jira.codehaus.org/browse/MGWT-226
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>         Environment: Apache Maven 3.0 (r1004208; 2010-10-04 07:50:56-0400)
> Java version: 1.6.0_22
> Java home: /opt/sun-jdk-1.6.0.22/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32.23" arch: "amd64" Family: "unix"
>            Reporter: jieryn
>         Attachments: MGWT-226.zip
>
>
> This is an official bug report from dialog on the user group: 
> http://groups.google.com/group/codehaus-mojo-gwt-maven-plugin-users/browse_thread/thread/f57640a247fd7422
> The commit which regressed the plugin is r12479; r12281 works as expected, 
> but r12479 fails. There's an awful lot going on in that commit, including 
> relocating the archtype, massive site updates, and more ITs.
> Anyhow, the classpath doesn't seem to be set up properly after r12479 ... as 
> things that used to be included in the classpath prior to r12479 are no 
> longer in the classpath -- specifically, dependencies listed in 
> project.dependencies. For example, I have a RemoteServiceServlet defined in a 
> dependency which is no longer being picked up.

-- 
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


Reply via email to