Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster
No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #701753] Mon, 25 July 2011 10:39 Go to next message
Gabriel F. is currently offline Gabriel F.
Messages: 3
Registered: July 2011
Junior Member
During an ANT-Task Buckminster shows the following error message.
In our target platform there is org.apache.commons.cli:osgi.bundle$1.2.0.v201105210650
Can anybody give me a hint what I can do to solve this problem?


init actor: jdt.ant[<myproject>:eclipse.feature$1.0.0.qualifier#start.task]
INFO:  [start <myproject>:eclipse.feature$1.0.0.qualifier#start.task]
ERROR: org.eclipse.buckminster.core.metadata.MissingComponentException: No component named org.apache.commons.cli.source:osgi.bundle/[1.2.0.v201105210650,1.2.0.v201105210650](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))) is known to Buckminster
org.eclipse.buckminster.core.metadata.MissingComponentException: No component named org.apache.commons.cli.source:osgi.bundle/[1.2.0.v201105210650,1.2.0.v201105210650](&(buckminster.download.source=true)(!(eclipse.p2.optional=false))) is known to Buckminster
	at org.eclipse.buckminster.core.metadata.WorkspaceInfo.resolveLocal(WorkspaceInfo.java:613)
	at org.eclipse.buckminster.core.metadata.WorkspaceInfo.getResolution(WorkspaceInfo.java:504)
	at org.eclipse.buckminster.core.metadata.ModelCache.findCSpec(ModelCache.java:46)
	at org.eclipse.buckminster.jdt.internal.BMClasspathContainer.addNodeToClassPath(BMClasspathContainer.java:116)
	at org.eclipse.buckminster.jdt.internal.BMClasspathContainer.addNodeToClassPath(BMClasspathContainer.java:117)
	at org.eclipse.buckminster.jdt.internal.BMClasspathContainer.addNodeToClassPath(BMClasspathContainer.java:117)
	at org.eclipse.buckminster.jdt.internal.BMClasspathContainer.<init>(BMClasspathContainer.java:44)
	at org.eclipse.buckminster.jdt.internal.ClasspathEmitter.appendPaths(ClasspathEmitter.java:115)
	at org.eclipse.buckminster.jdt.internal.ClasspathEmitter.finalClasspathResolve(ClasspathEmitter.java:80)
	at org.eclipse.buckminster.jdt.internal.actor.JdtAntActor.addActorPathGroups(JdtAntActor.java:41)
	at org.eclipse.buckminster.ant.actor.AntActor.internalPerform(AntActor.java:241)
	at org.eclipse.buckminster.core.actor.AbstractActor.perform(AbstractActor.java:195)
	at org.eclipse.buckminster.core.internal.actor.PerformManager$DirectActionInvocation.execute(PerformManager.java:143)
	at org.eclipse.buckminster.core.internal.actor.PerformManager.internalPerform(PerformManager.java:454)
	at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:293)
	at org.eclipse.buckminster.core.internal.actor.PerformManager.perform(PerformManager.java:305)
	at org.eclipse.buckminster.core.commands.Perform.internalRun(Perform.java:108)
	at org.eclipse.buckminster.core.commands.WorkspaceCommand.run(WorkspaceCommand.java:91)
	at org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(AbstractCommand.java:200)
	at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:317)
	at org.eclipse.buckminster.cmdline.Headless.run(Headless.java:136)
	at org.eclipse.buckminster.cmdline.Headless.start(Headless.java:156)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #701786 is a reply to message #701753] Mon, 25 July 2011 11:39 Go to previous messageGo to next message
Matthew Webber is currently offline Matthew Webber
Messages: 198
Registered: December 2010
Senior Member
What ANT-task are you trying to run? How was your target platform materialized?

And this may aound silly, but have you restarted your IDE since you materialized? Buckminster sometimes caches state that has in fact changed.
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #702393 is a reply to message #701786] Tue, 26 July 2011 05:51 Go to previous messageGo to next message
Gabriel F. is currently offline Gabriel F.
Messages: 3
Registered: July 2011
Junior Member
Materialisation is done via p2 sites.
I have cleared the workspace in jenkins but the problem still persists.


This is my ANT-task:

    <target name="start.mwe.workflow"">
        <java classname="org.eclipse.emf.mwe.core.WorkflowRunner" dir="." classpathref="classpath" output="build.log">
            [...]
        </java>
    </target>


The .cspex:


<?xml version="1.0" encoding="UTF-8"?>
<cspecExtension
    xmlns:bc="(..)"
    xmlns="(..)">
    <dependencies>
        <dependency name="org.eclipse.emf.mwe.core" componentType="osgi.bundle" versionDesignator="1.1.0" versionType="OSGi"/>
        <dependency name="org.apache.commons.logging" componentType="osgi.bundle" versionDesignator="1.0.4" versionType="OSGi"/>
        <dependency name="org.eclipse.xtend.typesystem.emf" componentType="osgi.bundle" versionDesignator="1.0.1" versionType="OSGi"/>
        <dependency name="org.eclipse.emf.mwe.utils" componentType="osgi.bundle" versionDesignator="1.1.0" versionType="OSGi"/>
        <dependency name="org.eclipse.xtend.profiler" componentType="osgi.bundle" versionDesignator="1.0.1" versionType="OSGi"/>
        <dependency name="org.eclipse.xtend" componentType="osgi.bundle" versionDesignator="1.1.0" versionType="OSGi"/>
        <dependency name="org.eclipse.emf.ecore.xmi" componentType="osgi.bundle" versionDesignator="2.7.0" versionType="OSGi"/>
        <dependency name="org.eclipse.xtend.util.stdlib" componentType="osgi.bundle" versionDesignator="1.0.1" versionType="OSGi"/>
        <dependency name="org.eclipse.xpand" componentType="osgi.bundle" versionDesignator="1.1.0" versionType="OSGi"/>        
    </dependencies>
    <actions>
        <public name="start.task" actor="jdt.ant">
            <actorProperties>
                <property key="buildFile" value="build.xml" />
                <property key="targets" value="start.mwe.workflow" />
            </actorProperties>
            <properties>
                [...]
            </properties>
            <products alias="destination" base="${buckminster.output}">
                <path path="output/" />
            </products>
        </public>
    </actions>
</cspecExtension>


Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #725253 is a reply to message #702393] Wed, 14 September 2011 07:29 Go to previous messageGo to next message
js Missing name is currently offline js Missing name
Messages: 73
Registered: July 2009
Member
I have a related problem:

http://www.eclipse.org/forums/index.php/t/209520/

and never found a solution Sad I also get this one:

No component named org.apache.commons.logging.source:osgi.bundle/[1.1.1.v201005080502,1.1.1.v201005080502] is known to Buckminster

but cannot find any update sites that have the 1.1.1.v201005080502 version of that plugin.


Could be nice if bucky could produce information on which bundle/feature has a require on the specified version (have tried to save the .cspec file but it does not give any information on this).

[Updated on: Wed, 14 September 2011 07:45]

Report message to a moderator

Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #735976 is a reply to message #725253] Thu, 13 October 2011 05:27 Go to previous messageGo to next message
Andreas Schilling is currently offline Andreas Schilling
Messages: 22
Registered: April 2010
Junior Member
I'm also having probably the same problem.
On our Buildserver (Jenkins) everything is fine, however if I want to do a local build from Eclipse (run the respective action that is defined in the CSPEX and that is also used on the buildserver) I get this error for at least one bundle (actually only one error is logged but when using more fine grained logging I see it on several bundles happen).
having a look at the dependency graph shows, that it seems like all *.source bundles of third party libraries are missing, e.g. com.springsource.javax.validation.source
the message then is
No component named com.springsource.javax.validation.source:osgi.bundle$0.0.0#Raw Omni Version is known to Buckminster

I don't really understand why that happens. first I thought that buckminster somehow does not use our target platform (which contains the bundle) when doing the local build but then again it should show ALL bundles to be unresolved and not only the source bundles (or shouldn't it?).
Btw, the manifest of that specific bundle seems to be not 100% correct to me, however for other bundles that also can't be resolved I can see problems on the first glance, so it might have something to do with it or not...

while in theory everything is fine as long as the Jenkins build does not fail I still would like to be able to work with buckminster on my development machine as well Razz
also, I can't tell you why and when things stopped working locally, because some 1 1/2 years ago when we were setting up the buckminster process everything worked from Eclipse as well.

regards,

Andreas
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #735987 is a reply to message #735976] Thu, 13 October 2011 05:50 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
What version of Buckminster are you running? There's been a recent fix for missing source bundles.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=357060

- thomas

On 2011-10-13 11:27, Andreas Schilling wrote:
> I'm also having probably the same problem.
> On our Buildserver (Jenkins) everything is fine, however if I want to do a local build from Eclipse (run the respective
> action that is defined in the CSPEX and that is also used on the buildserver) I get this error for at least one bundle
> (actually only one error is logged but when using more fine grained logging I see it on several bundles happen).
> having a look at the dependency graph shows, that it seems like all *.source bundles of third party libraries are
> missing, e.g. com.springsource.javax.validation.source
> the message then is
> No component named com.springsource.javax.validation.source:osgi.bundle$0.0.0#Raw Omni Version is known to Buckminster
> I don't really understand why that happens. first I thought that buckminster somehow does not use our target platform
> (which contains the bundle) when doing the local build but then again it should show ALL bundles to be unresolved and
> not only the source bundles (or shouldn't it?).
> Btw, the manifest of that specific bundle seems to be not 100% correct to me, however for other bundles that also can't
> be resolved I can see problems on the first glance, so it might have something to do with it or not...
>
> while in theory everything is fine as long as the Jenkins build does not fail I still would like to be able to work with
> buckminster on my development machine as well :p
> also, I can't tell you why and when things stopped working locally, because some 1 1/2 years ago when we were setting up
> the buckminster process everything worked from Eclipse as well.
>
> regards,
>
> Andreas
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #736017 is a reply to message #735987] Thu, 13 October 2011 07:14 Go to previous messageGo to next message
Andreas Schilling is currently offline Andreas Schilling
Messages: 22
Registered: April 2010
Junior Member
I just set up a new eclipse with a fresh buckminster today (from the update site), it says it is 1.4.0.v20110915-1108

I assume the bug should be fixed in there?
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #736026 is a reply to message #736017] Thu, 13 October 2011 07:32 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-10-13 13:14, Andreas Schilling wrote:
> I just set up a new eclipse with a fresh buckminster today (from the update site), it says it is 1.4.0.v20110915-1108
>
> I assume the bug should be fixed in there?

It should, yes.

- thomas
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #736040 is a reply to message #736026] Thu, 13 October 2011 08:43 Go to previous messageGo to next message
Andreas Schilling is currently offline Andreas Schilling
Messages: 22
Registered: April 2010
Junior Member
Sad

but thanks for the help so far!
any further hints how I can debug such an issue? I still feel that I just might be missing some rather simple point. I wouldn't consider myself a buckminster expert, so that's quite likely Smile
EDIT: I just saw that "BJ" seems to have exactly the same problem (the other thread opened today)

regards,

Andreas

[Updated on: Thu, 13 October 2011 08:49]

Report message to a moderator

Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #886703 is a reply to message #736040] Fri, 15 June 2012 09:47 Go to previous messageGo to next message
Andreas Schilling is currently offline Andreas Schilling
Messages: 22
Registered: April 2010
Junior Member
so, we're still struggling with that error, it's really driving us crazy.
some small progresses have been made though.
in the cquery we can include advisor nodes to skip the strange source bundles.
however, when invoking an action this does not help at all.

what is strange and something we definitely do not understand is, why these source bundles are listed as direct dependencies of our product (if we open the dependencies view in eclipse). in no dependency anywhere in our bundles these source bundles are referenced.
does someone have an idea how that happens?

thanks for any hints in advance!
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #892258 is a reply to message #886703] Wed, 27 June 2012 10:11 Go to previous messageGo to next message
Dennis Huebner is currently offline Dennis Huebner
Messages: 204
Registered: July 2009
Senior Member

Hi Andreas ,
can you provide an example project, which I can try to run with my buckminster installation?
github or something?

Regards,
Dennis.



+Dennis Hübner

--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #1385384 is a reply to message #892258] Fri, 06 June 2014 01:07 Go to previous messageGo to next message
Al B is currently offline Al B
Messages: 129
Registered: July 2009
Senior Member
Did anyone find workaround for this? With Juno, we are able to create build artifacts, but when we try with Kepler 4.3, then we get this exception:

Problem during meta-data refresh: No component named _feature_gov.nasa.arc.spife is known to Buckminster
org.eclipse.buckminster.core.metadata.MissingComponentException: No component named _feature_gov.nasa.arc.spife is known to Buckminster
at org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:179)
at org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:185)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer.refreshProject(MetadataSynchronizer.java:295)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer.workspaceCatchUp(MetadataSynchronizer.java:394)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer$WorkspaceCatchUpJob.run(MetadataSynchronizer.java:185)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #1385389 is a reply to message #1385384] Fri, 06 June 2014 02:10 Go to previous message
Lorenzo Bettini is currently offline Lorenzo Bettini
Messages: 1325
Registered: July 2009
Senior Member
On 06/06/2014 07:07, Al B wrote:
> Did anyone find workaround for this? With Juno, we are able to create
> build artifacts, but when we try with Kepler 4.3, then we get this
> exception:
>
> Problem during meta-data refresh: No component named
> _feature_gov.nasa.arc.spife is known to Buckminster
> org.eclipse.buckminster.core.metadata.MissingComponentException: No
> component named _feature_gov.nasa.arc.spife is known to Buckminster
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:179)
>
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:185)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer.refreshProject(MetadataSynchronizer.java:295)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer.workspaceCatchUp(MetadataSynchronizer.java:394)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer$WorkspaceCatchUpJob.run(MetadataSynchronizer.java:185)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Hi

do you get this error in the IDE or during the headless build? Are you
using Buckminster for Kepler?

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
Previous Topic:buckminster 4.2 requires jgit [2.0.0,3.0.0), but current jgit is 3.3.2
Next Topic:problems with http://download.cloudsmith.com
Goto Forum:
  


Current Time: Sun Aug 31 04:44:19 EDT 2014

Powered by FUDForum. Page generated in 0.02371 seconds