Comment 1 Michael Vorburger 2016-07-25 12:01:39 EDT

Raising Importantce, because I'm actually fairly regularly seeing a very similar looking exception not anymore on Project Import, but during normal workspace builds, for any Maven plugin such as standard maven-resources-plugin & build-helper-maven-plugin and not (only) maven-checkstyle-plugin as above - making me thing that this is some more serious problem in Maven core, not just one plugin that got something wrong... check these out:


Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:3.0.1:resources failed: Unable to load the mojo 'resources' (or one of its required components) from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1' (org.apache.maven.plugins:maven-resources-plugin:3.0.1:resources:default-resources:process-resources)

org.apache.maven.plugin.PluginExecutionException: Execution default-resources of goal org.apache.maven.plugins:maven-resources-plugin:3.0.1:resources failed: Unable to load the mojo 'resources' (or one of its required components) from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
    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:735)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
    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 'resources' (or one of its required components) from the plugin 'org.apache.maven.plugins:maven-resources-plugin:3.0.1'
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:551)
    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: org.apache.maven.plugins:maven-resources-plugin:3.0.1:resources
    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:517)
    ... 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



and:


Description Resource    Path    Location    Type
Execution add-yang-sources of goal org.codehaus.mojo:build-helper-maven-plugin:1.10:add-source failed: Unable to load the mojo 'add-source' (or one of its required components) from the plugin 'org.codehaus.mojo:build-helper-maven-plugin:1.10' (org.codehaus.mojo:build-helper-maven-plugin:1.10:add-source:add-yang-sources:generate-sources)

org.apache.maven.plugin.PluginExecutionException: Execution add-yang-sources of goal org.codehaus.mojo:build-helper-maven-plugin:1.10:add-source failed: Unable to load the mojo 'add-source' (or one of its required components) from the plugin 'org.codehaus.mojo:build-helper-maven-plugin:1.10'
    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:735)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
    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 'add-source' (or one of its required components) from the plugin 'org.codehaus.mojo:build-helper-maven-plugin:1.10'
    at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:551)
    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: org.codehaus.mojo:build-helper-maven-plugin:1.10:add-source
    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:517)
    ... 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
    pom.xml /org.opendaylight.netvirt.aclservice-api    line 11 Maven Build Problem

Comment 2 Michael Vorburger 2016-07-25 12:07:47 EDT

https://issues.apache.org/jira/browse/FELIX-5017 => https://issues.apache.org/jira/browse/FELIX-4882 shows something similarly looking, but my understanding of Maven internals is too limited to understand the parallel - and what could possibly be done about fixing it where.

Comment 3 Michael Vorburger 2017-01-13 09:18:39 EST

Bug 510439 raised in Sisu to see if this could get some attention there...

https://issues.apache.org/jira/browse/MNG-6157 raised in Maven core; dito.

Sorry for now having opened multiple bugs, but I'm hitting this almost daily since half a year, so perhaps this will help get it some attention and traction..

Comment 4 Michael Vorburger 2017-01-13 09:25:25 EST

Would there be anything I can do to help get to the bottom of this?  My understanding of Maven / Plexus / Sisu internals is sketchy at best, but I could e.g. set breakpoints in places you tell me, if that would add any value to understand what's going on here and how to eventually resolve it?

Comment 5 Igor Fedorenko 2017-01-13 09:32:47 EST

Intermittent problems are very difficult to debug and personally I simply don't have the time to chase a bug I may or may not be able to reproduce. I assume other committers are in the same position. A way to reproduce the problem reliably will increase the chance somebody will have a look.

Comment 6 Michael Vorburger 2017-01-13 09:54:58 EST

Igor, Thank You for everything you've done for Maven and M2E!

Fully understand a reliable reproducer would be ideal, but sometimes it's not easy to provide simple steps with an isolated dummy project to reproduce problems. 

If anyone would you be willing to look into it using a more elaborate set-up, it is easy to see, if you're willing to sink a little bit of time into setting up a WS based on https://github.com/vorburger/opendaylight-eclipse-setup; which is all completely FLOSS (the setup model as well as the projects it loads).  If the README there isn't clear, I can provide further steps here, if there's interest.

BTW, just in case the stack trace above involves a bit too many animals for your taste: The stack trace I just posted over on https://issues.apache.org/jira/browse/MNG-6157 is much shorter than the one shown above (minus org.eclipse.oomph, minus com.basistech m2e-code-quality; and on core maven-resources-plugin instead of maven-checkstyle-plugin), but I strongly suspect it's all the same problem.

I could dig more into it as well, if you could provide some guidance to enable me to debug this further?  I admit barely understand what's actually going on here internally.. 

So M2E is trying to run executeMojo of a Maven plugin (maven-resources-plugin:3.0.1, in the case of the stack shown on MNG-6157), but then that mojo can no longer be found, due to a NoSuchElementException?

Is it possible that e.g. some/one of the many Maven plugins used as part of the projects provisioned by opendaylight-eclipse-setup misbehave somehow and could be causing this?  Or unlikely that "bad" plugins could screw this? 

A concurrency issue then - does M2E internally run related to what's happening in the stack shown on MNG-6157 concurrently?

Are you guys (M2E maintainers) on IRC / mattermost.eclipse.org / gitter.im somewhere to chat, some time?

Comment 7 Igor Fedorenko 2017-01-13 10:30:57 EST

I won't have time to look at this, sorry. Also, we generally expect problems reported against m2e to be reproducible either with m2e installed on top of clean/fresh Eclipse SDK or with clean/fresh Eclipse for Java Developers. It is not reasonable or fair to expect us to spend time to understand how the many thirdparty tools installed as part of opendaylight-eclipse-setup interact with each other, regardless whether the tools are FLOSS or not.

Comment 8 Michael Vorburger 2017-01-13 10:59:33 EST

> Is it possible that e.g. some/one of the many Maven plugins used

actually, https://issues.apache.org/jira/browse/FELIX-5017 does connect this specifically to something done wrong in an old version of the maven-bundle-plugin, which apparently https://issues.apache.org/jira/browse/FELIX-4882 fixed in their 3.0.0.

now, the projects we're hitting this on uses maven-bundle-plugin v3.0.1, so that's probably not the culprit - but it still seems to indicate that this problem can be caused by issues in particular Maven plugins?

If this analysis is correct, then something worth trying when hitting this again is to do a lifecycle mapping ignore for even more Maven plugins than we already do.  The one in particular I have in mind is the org.apache.aries.blueprint:blueprint-maven-plugin, which was on mapping execute in at least some the projects we're hitting this.  I've just changed that to ignore; let's see if that helps to make this never occur again...

Comment 9 Michael Vorburger 2017-01-13 19:47:34 EST

> lifecycle mapping ignore for even more Maven plugins

just happened again, for a project that did not even have blueprint-maven-plugin, but which had  on 'execute' the build-helper-maven-plugin (latest version 1.12..) and "resources:resources" & testResources, but nothing else (many others; but most on "ignore"; only "configurator" for checkstyle, compile) .. and touching the pom.xml made it go away again, so no repro.

Comment 10 Eclipse Genie 2018-11-14 00:48:10 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 11 Pino Silvaggio 2019-02-04 21:28:33 EST

I just got this problem too.

Description	Resource	Path	Location	Type
Execution default of goal org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0:generate failed: Unable to load the mojo 'generate' (or one of its required components) from the plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0' (org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0:generate:default:generate-sources)

org.apache.maven.plugin.PluginExecutionException: Execution default of goal org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0:generate failed: Unable to load the mojo 'generate' (or one of its required components) from the plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0'
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:156)
	at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:334)
	at org.eclipse.m2e.core.internal.embedder.MavenImpl.lambda$8(MavenImpl.java:1401)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
	at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1400)
	at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
	at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:150)
	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:177)
	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:106)
	at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
	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:87)
	at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:199)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:798)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:219)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:262)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:315)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:318)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:370)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:391)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:145)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.apache.maven.plugin.PluginContainerException: Unable to load the mojo 'generate' (or one of its required components) from the plugin 'org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0'
	at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:557)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:124)
	... 30 more
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
      role: org.apache.maven.plugin.Mojo
  roleHint: org.jvnet.jaxb2.maven2:maven-jaxb2-plugin:0.14.0:generate
	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:520)
	... 31 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)
	... 33 more
	pom.xml	/connector-newskies	line 91	Maven Build Problem

Comment 12 Michael Vorburger 2019-02-05 05:32:53 EST

(In reply to Pino Silvaggio from comment #11)
> I just got this problem too.

Pino, it's some concurrency issue - it goes away if you retry.

Sometimes you have to manually delete the problem marker.

Comment 13 Denis Roy 2021-04-19 13:24:25 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/