java.lang.NoClassDefFoundError: com/totsp/mavenplugin/gwt/support/MakeCatalinaBase

[Simon Kingaby]

I am trying to get the gwt maven2 plugin to work. I do not have
tomcat installed.
I am getting this error in the gwt:compile
java.lang.NoClassDefFoundError: com/totsp/mavenplugin/gwt/support/
MakeCatalinaBase

I am not sure if this error is because I have something in the pom set
up wrong, or because the src folder structure and file locations are
set up wrong.

Any suggestions?

Also, I downloaded the sample off this list and can't build that
because I don't have tomcat. Should I just put tomcat on my build
machine. (Note: this is not the dev workstation, but rather the
dedicated build machine.)

Thanks,
Simon

[Simon Kingaby]

Also, I have installed TomCat now. No help.

I am trying to get the example app to compile. I worked through
several issues but now I am stuck again at this error:

[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] com/totsp/mavenplugin/gwt/support/MakeCatalinaBase
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError: com/totsp/mavenplugin/gwt/support/
MakeCatalinaBa
se
at
com.totsp.mavenplugin.gwt.AbstractGWTMojo.makeCatalinaBase(AbstractGW
TMojo.java:439)
at
com.totsp.mavenplugin.gwt.CompileMojo.execute(CompileMojo.java:59)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

[Werner Thiemann]

Hello Simon,

could you please post your POM-file here, so we can get more
information. Thank you.

[Dan Diephouse]

I'm just guessing, but do you have the path to the gwt install set
correctly in the war pom.xml?

[ahhughes]

I've been running this on Windows occasionally, and I have noticed
that spaces in the GWT paths run havock on the plugin.

I had to change things like..

c:\Program Files\gwt-windows-1.4.60
...to...
c:\progra~1\gwt-windows-1.1.60