Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Validation error with maven-bundle-plugin "Unable to load the mojo 'manifest'"

Hi AURÉLIEN,
the Maven-Bundle-Plugin since version 3.2.0 supports M2E natively (https://issues.apache.org/jira/browse/FELIX-4009). Unfortunately that conflicts with m2e-tycho (https://github.com/tesla/m2eclipse-tycho). Since the latter also does no longer seem to be maintained (when it comes to maven-bundle-plugin) you can prevent the error by just removing that extension from Eclipse. Actually the exception comes from that extension.
Konrad

> On 12. Apr 2017, at 15:56, Aurelien Pupier <apupier@xxxxxxxxxx> wrote:
> 
> Hello,
> 
> I'm experiencing validation error reported with the following message
> Execution m2e-tycho:default-bundle:manifest of goal org.apache.felix:maven-bundle-plugin:3.2.0:manifest failed: Unable to load the mojo 'manifest' (or one of its required components) from the plugin 'org.apache.felix:maven-bundle-plugin:3.2.0' (org.apache.felix:maven-bundle-plugin:3.2.0:bundle:default-bundle:package)
> 
> The stack reported is the followning:
> 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.sonatype.tycho.m2e.felix.internal.MavenBundlePluginConfigurator$1.build(MavenBundlePluginConfigurator.java:125)
>  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 'manifest' (or one of its required components) from the plugin 'org.apache.felix:maven-bundle-plugin:3.2.0'
>  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.felix:maven-bundle-plugin:3.2.0:manifest
>  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
> 
> With some trace activated, in my logs, i spotted this trace
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:166)
> 	... 31 more
> Caused by: java.lang.NoClassDefFoundError: aQute/bnd/osgi/ClassDataCollectors$Collectors
> 	at aQute.bnd.osgi.Analyzer.analyze(Analyzer.java:213)
> 	at aQute.bnd.osgi.Builder.analyze(Builder.java:389)
> 	at aQute.bnd.osgi.Analyzer.calcManifest(Analyzer.java:687)
> 	at aQute.bnd.osgi.Builder.build(Builder.java:105)
> 	at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:969)
> 	at org.apache.felix.bundleplugin.ManifestPlugin.getAnalyzer(ManifestPlugin.java:247)
> 	at org.apache.felix.bundleplugin.ManifestPlugin.execute(ManifestPlugin.java:98)
> 	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:384)
> 	at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:375)
> 	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> 	... 31 more
> Caused by: java.lang.ClassNotFoundException: aQute.bnd.osgi.ClassDataCollectors$Collectors
> 	at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> 	at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> 	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> 	at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> 	... 41 more
> 
> From y understanding it means that something is missing a dependency on bndlib.
> Is it the maven jars provided by org.eclipse.m2e.maven.runtime?
> Is it the maven-bundle-plugin?
> 
> My Eclipse is crashing most of the time when I tried to put breakpoints so hard to investigate.
> 
> Do you have any ideas on what I should try? What should I check?
> 
> Regards,
> 
> 
> -- 
> AURÉLIEN PUPIER
> SENIOR SOFTWARE ENGINEER, FUSE TOOLING
> Red Hat France
> apupier@xxxxxxxxxx    IM: apupier
> 
> 
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/m2e-users



Back to the top