2.5.1 generateAsync exception: basedir does not exist

296 views
Skip to first unread message

Shannon Carey

unread,
Nov 20, 2014, 11:07:17 AM11/20/14
to codehaus-mojo-gwt-...@googlegroups.com
I am using gwt-maven-plugin 2.5.1. When running jgitflow:release-finish, which subsequently runs "mvn clean deploy ...", the build fails when it gets to the gwt generateAsync goal that I have bound to the generate-sources phase in one of my GWT modules. The exception is:

    [INFO] --- gwt-maven-plugin:2.5.1:generateAsync (gwt-generate-async) @ shared ---
    [ERROR] Failed to generate Async interface
    java.lang.IllegalStateException: basedir /redacted/portal/shared/target/generated-sources/annotations does not exist
        at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
        at org.codehaus.mojo.gwt.GenerateAsyncMojo.scanAndGenerateAsync(GenerateAsyncMojo.java:182)
        at org.codehaus.mojo.gwt.GenerateAsyncMojo.execute(GenerateAsyncMojo.java:154)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions(MojoExecutor.java:364)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:198)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)


Sure enough, the target/generated-sources directory only contains a "gwt" folder.

Strangely, the problem doesn't happen when I run a plain old "mvn install", even though the "annotations" folder it complains about never exists.

This seems like a bug in GenerateAsyncMojo where it should be checking whether each sourceRoot folder exists before creating a scanner on it, but that doesn't really help me. Does anyone have any ideas about a workaround?

Shannon Carey

unread,
Nov 20, 2014, 11:15:06 AM11/20/14
to codehaus-mojo-gwt-...@googlegroups.com
I should note that I recently refactored this GWT project into separate Maven modules for server, client, and shared code so that might have something to do with it.
Reply all
Reply to author
Forward
0 new messages