I don't mess with anything wrt gwt versions - so what ever is used in master is what
I'm using. I am able to debug my gwt app using the normal JPDA mechanisms and dev
mode.
I did do a clean build in the sense that I deleted all target directories and rebuilt from
root. I didn't purge my local mvn repo or anything like that.
----- Original Message -----
I have seen this kind of thing before. It usually occurs when the
client gets
out of sync with the server. Usually doing a clean rebuild of everything
alleviates it.
And you are using the 2.4.0 version of GWT for dev work right (as they have
broke some of the dev mode stuff in 2.5.0)?
— Mike
On 8 Apr 2014, at 16:48, John Mazzitelli <mazz(a)redhat.com> wrote:
> Anyone ever see this? I did add something to the GWT interfaces, but there
> are no errors to indicate anything is wrong with the new code... there
> isn't anything obviously wrong with my new code that I can see.
>
> Caused by: org.codehaus.mojo.gwt.shell.ForkedProcessExecutionException:
> Command [[
> ...the big command line to run the gwt compiler is here...
> ]] failed with status 1
> at
>
org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo$JavaCommand.execute(AbstractGwtShellMojo.java:485)
> at
> org.codehaus.mojo.gwt.shell.CompileMojo.compile(CompileMojo.java:365)
> at
> org.codehaus.mojo.gwt.shell.CompileMojo.doExecute(CompileMojo.java:280)
> at
>
org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:172)
> at
>
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
>
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel