Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'

From: Igor Fedorenko <igor@xxxxxxxxxxxxxx>
Date: Thu, 23 Apr 2015 07:51:11 -0400
Delivered-to: m2e-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/m2e-users>
List-help: <mailto:m2e-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/m2e-users>, <mailto:m2e-users-request@eclipse.org?subject=unsubscribe>

Hmm. Indeed. Looks like release aggregator job didn't pick official m2e
1.6/m6 build but used one of the staged builds instead. Good thing m7
isn't too far away.

-- 
Regards,
Igor

On Thu, Apr 23, 2015, at 07:39 AM, Robert Munteanu wrote:
> On Thu, Apr 23, 2015 at 2:16 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx>
> wrote:
> > Where did you install 1.6.0-20150324-2020 from?
> 
> It's a stock Eclipse Mars installation, I do not have any m2e-specific
> update sites installed.
> 
> >
> > You need to use m2e 1.6.0.20150325-2013 or newer. It includes fix for
> > bug 463075 [1], which was causing the problem you see.
> 
> Ah, thanks. I've added the
> http://download.eclipse.org/technology/m2e/milestones/1.6/ update site
> to my installation and upgraded m2e.
> 
> Robert
> 
> >
> > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=463075
> >
> > --
> > Regards,
> > Igor
> >
> > On Thu, Apr 23, 2015, at 05:31 AM, Robert Munteanu wrote:
> >> Hi,
> >>
> >> I'm using m2e 1.6.0-20150324-2020 with the Tycho Project Configurators
> >> 0.6.0.20120730215 ( but have seem the same error with the Tycho
> >> Project Configurators 0.9.0 ).
> >>
> >> Project with 'bundle' packaging type seem to randomly fail
> >> configuration, and an error is logged ( see end of email ).
> >>
> >> The error only disappears when I update the project configuration
> >> _and_ force update of snapshots/releases. Has anyone seen similar
> >> errors? I do not recall having these issues with previous version of
> >> m2e.
> >>
> >> Thanks,
> >>
> >> Robert
> >>
> >> Execution m2e-tycho:default-bundle:manifest of goal
> >> org.apache.felix:maven-bundle-plugin:2.5.0:manifest failed: Unable to
> >> load the mojo 'manifest' (or one of its required components) from the
> >> plugin 'org.apache.felix:maven-bundle-plugin:2.5.0'
> >> (org.apache.felix:maven-bundle-plugin:2.5.0:bundle:default-bundle:package)
> >>
> >> org.apache.maven.plugin.PluginExecutionException: Execution
> >> m2e-tycho:default-bundle:manifest of goal
> >> org.apache.felix:maven-bundle-plugin:2.5.0:manifest failed: Unable to
> >> load the mojo 'manifest' (or one of its required components) from the
> >> plugin 'org.apache.felix:maven-bundle-plugin:2.5.0'
> >>     at
> >>     org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:153)
> >>     at
> >>     org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:332)
> >>     at
> >>     org.eclipse.m2e.core.internal.embedder.MavenImpl$11.call(MavenImpl.java:1379)
> >>     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:1377)
> >>     at
> >>     org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:52)
> >>     at
> >>     org.sonatype.tycho.m2e.internal.AbstractMavenBundlePluginProjectConfigurator$1.build(AbstractMavenBundlePluginProjectConfigurator.java:132)
> >>     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 'manifest' (or one of its required components) from the
> >> plugin 'org.apache.felix:maven-bundle-plugin:2.5.0'
> >>     at
> >>     org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:576)
> >>     at
> >>     org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:121)
> >>     ... 32 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:2.5.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:543)
> >>     ... 33 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)
> >>     ... 35 more
> >>     pom.xml    /oak-solr-core    line 67    Maven Build Problem
> >>
> >>
> >> --
> >> http://robert.muntea.nu/
> >> _______________________________________________
> >> 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
> > _______________________________________________
> > 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
> 
> 
> 
> -- 
> http://robert.muntea.nu/
> _______________________________________________
> 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

References:
- [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'
  - From: Robert Munteanu
- Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'
  - From: Igor Fedorenko
- Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'
  - From: Robert Munteanu

Prev by Date: Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'
Next by Date: [m2e-users] Eclipse multi module Maven project problems - automatic install + debugging
Previous by thread: Re: [m2e-users] Intermittent errors with m2e 1.6.0 and the Tycho Project Configurators - Unable to load the mojo 'manifest'
Next by thread: [m2e-users] Eclipse multi module Maven project problems - automatic install + debugging
Index(es):
- Date
- Thread

Breadcrumbs