maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4443) gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]
Date Fri, 13 Nov 2009 23:46:55 GMT


Benjamin Bentmann closed MNG-4443.

    Resolution: Not A Bug
      Assignee: Benjamin Bentmann

I managed to reproduce the compilation failure when using gwt-maven-plugin:1.0 with both Maven
2.2.1 and Maven 3.0-alpha-3. The project builds fine as soon as the gwt-maven-plugin is locked
down to version 1.1, again with both Maven 2.2.1 and 3.0-alpha-3. So it's just a matter of
specifying the correct plugin version.

The difference between Maven 2 and 3 in case of a missing plugin version results from the
current metadata for gwt-maven-plugin:
<?xml version="1.0" encoding="UTF-8"?>
which lists latest=1.1 but release=1.0. Maven 3 intentionally prefers "release" over "latest".
Given the version 1.1 of the plugin has neither sources nor javadoc, I guess the release manager
did not use the Maven Release Plugin, thereby producing a bad plugin release.

> gwt-maven-plugin + gwt-2.0.0-ms2: GWTCompiler failed -> [Help 1]
> ----------------------------------------------------------------
>                 Key: MNG-4443
>                 URL:
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Plugins and Lifecycle
>    Affects Versions: 3.0-alpha-3
>         Environment: Mac OS X 10.5.8, Windows XP SP2
>            Reporter: Tiago Fernandez
>            Assignee: Benjamin Bentmann
>         Attachments: build.log, pom.xml
> I am used to build my GWT app ( with Maven 2.x
without any problem, but when I try a clean packaging with Maven 3.0-alpha-3 I get the following
> [ERROR] GWTCompiler failed -> [Help 1]
> org.apache.maven.plugin.MojoExecutionException: GWTCompiler failed
> 	at org.codehaus.mojo.gwt.CompileMojo.compile(
> 	at org.codehaus.mojo.gwt.CompileMojo.execute(
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
> 	at org.apache.maven.DefaultMaven.doExecute(
> 	at org.apache.maven.DefaultMaven.execute(
> 	at org.apache.maven.cli.MavenCli.execute(
> 	at org.apache.maven.cli.MavenCli.doMain(
> 	at org.apache.maven.cli.MavenCli.main(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(
> 	at org.codehaus.plexus.classworlds.launcher.Launcher.main(
> 	at org.codehaus.classworlds.Launcher.main(
> I have attached the build.log with debug logs and exception traces and the pom.xml I'm
> If you need more details, feel free to ask me. Thanks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message