Missing test super source exception

[tbroyer]

Missing test super source exception

[branflake2267]

I think it may be crashing on my enhanced JDO source.

[branflake2267]

I think that's exactly what's happening. Datanucleus enhances the files, then when mojo executes add super sources, it crashes.

[branflake2267]

Little bit different exception, same process I think.

Execution generate-module of goal net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5:generate-module failed: Unable to load the mojo 'generate-module' (or one of its required components) from the plugin 'net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5' (net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5:generate-module:generate-module:generate-resources)

org.apache.maven.plugin.PluginExecutionException: Execution generate-module of goal net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5:generate-module failed: Unable to load the mojo 'generate-module' (or one of its required components) from the plugin 'net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5'
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:331)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1362)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1360)
    at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
    at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:137)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:172)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1$1.call(MavenBuilder.java:115)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod$1.call(MavenBuilder.java:105)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
    at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:86)
    at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:200)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:205)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:245)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:300)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:303)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:359)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:382)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load the mojo 'generate-module' (or one of its required components) from the plugin 'net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5'
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:579)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:121)
    ... 31 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
      role: org.apache.maven.plugin.Mojo
  roleHint: net.ltgt.gwt.maven:gwt-maven-plugin:1.0-rc-5:generate-module
    at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
    at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:546)
    ... 32 more
Caused by: java.util.NoSuchElementException
    at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next(RealmFilteredBeans.java:118)
    at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next(RealmFilteredBeans.java:1)
    at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:76)
    at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next(DefaultPlexusBeans.java:1)
    at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263)
    ... 34 more

[branflake2267]

I'm closing after finding a phase that worked.

<execution>
            <id>gwt-generate</id>
            <phase>validate</phase>
            <goals>
              <goal>generate-module</goal>
              <goal>add-super-sources</goal>
            </goals>
          </execution>

[branflake2267]

My eclipse dev and production behave slightly differently. In production, I can't get this to work.

[branflake2267]

Hm, just as I say that, seems this is working at the moment.

 <execution>
            <id>gwt-generate</id>
            <phase>intialize</phase>
            <goals>
              <goal>generate-module</goal>
              <goal>add-super-sources</goal>
            </goals>
          </execution>

[branflake2267]

I take that back, the issue was always there, just wasn't marked. Looks like the datanucleus is enhancing before the m2e runs. I can't seem to find a configuration that will run the goals before/after datanucleus. Or I'm just totally missing the issue still.

[tbroyer]

I don't get why project classes would break a Maven goal that doesn't use them; moreover it's not breaking "a Maven goal", but breaking Maven itself!
I'm afraid this must be unrelated to the plugin and rather an issue with Maven (or more probably its integration in Eclipse)

[branflake2267]

I've never seen any other maven plugin throw an exception and not sure why this one would throw it.

[tbroyer]

Googling the exception, it apparently happened to others; :

• https://github.com/cmoulliard/droolsjbpm-osgi-examples/issues/3
• https://vzurczak.wordpress.com/2014/07/23/another-cryptic-message-from-maven/
• etc.

[branflake2267]

I've noticed it in other places. What I'm hoping is if I get something else solved it might go away. The exception is also obscure for me b/c I can't see the entire stack trace.

[branflake2267]

Just a note, I saw this issue pop up on war packaging. So it feels like it's definitely upstream, in some other library.