| No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #701753] |
Mon, 25 July 2011 14:39  |
Eclipse User |
|
|
|
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 #702393 is a reply to message #701786] |
Tue, 26 July 2011 09:51  |
| Eclipse User |
|
|
|
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 #735976 is a reply to message #725253] |
Thu, 13 October 2011 09:27 |
| Eclipse User |
|
|
|
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 
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 09:50 |
| Eclipse User |
|
|
|
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 #886703 is a reply to message #736040] |
Fri, 15 June 2012 13:47 |
| Eclipse User |
|
|
|
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 #1385384 is a reply to message #892258] |
Fri, 06 June 2014 05:07 |
| Eclipse User |
|
|
|
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 06:10 |
| Eclipse User |
|
|
|
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
|
|
|
| Re: No component named org.apache.commons.cli.source:osgi.bundle/ known to Buckminster [message #1551499 is a reply to message #701753] |
Wed, 07 January 2015 17:12 |
| Eclipse User |
|
|
|
I am gettng this weird error and not able to see why this org.eclipse.emf.ecoretools.design:eclipse.feature is not getting resolved when i have this in my rmap {http://download.eclipse.org/modeling/emf/updates/releases/?importType=binary}
Buildfile: /home/chakraborty/workspace/temp/maps.releng/build.ant
[delete] Deleting: /home/chakraborty/workspace/temp/maps.releng/some.tmp.file
common.cleanup:
install.buckminster.headless:
[delete] Deleting: /home/chakraborty/workspace/temp/maps.releng/some.tmp.file
install.buckminster.headless.internal:
buckminster:
[echo] IMPORTANT: Populating an empty target platform may took over 10 minutes.
[echo] build.properties: /home/chakraborty/workspace/temp/maps.releng/build.properties
[java] INFO: setpref 'targetPlatformPath=/home/chakraborty/workspace/temp/buildroot/target.platform'
[java] INFO: resolve '/home/chakraborty/workspace/temp/maps.releng/build.cquery'
[java] ERROR [0002] : No suitable provider for component org.eclipse.emf.ecoretools.design:eclipse.feature was found in resourceMap file:/home/chakraborty/workspace/temp/maps.releng/build.rmap
[java] ERROR [0002] : No suitable provider for component org.eclipse.emf.ecoretools.design:eclipse.feature was found in searchPath eclipse
[java] ERROR [0002] : Rejecting provider p2({0}[http://download.eclipse.org/releases/juno]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/modeling/emf/updates/releases/?importType=binary[http://download.eclipse.org/modeling/emf/updates/releases/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/modeling/mdt/ocl/updates/releases/?importType=binary[http://download.eclipse.org/modeling/mdt/ocl/updates/releases/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://update.toem.de/?importType=binary[http://update.toem.de/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/birt/update-site/4.3/?importType=binary[http://download.eclipse.org/birt/update-site/4.3/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2({0}[http://download.eclipse.org/tools/cdt/releases/8.5]): No component match was found
[java] WARNING [0018] : Component request org.apache.commons.codec:osgi.bundle/[1.3.0.v201101211617,1.3.0.v201101211617] is in conflict with request org.apache.commons.codec:osgi.bundle/[1.4.0.v201209201156,1.4.0.v201209201156]
[java] WARNING [0036] : Component request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit:osgi.bundle/[4.10.0.v4_10_0_v20120426-0900,4.10.0.v4_10_0_v20120426-0900]
[java] WARNING [0040] : Component request org.apache.commons.logging:osgi.bundle/[1.1.1.v201101211721,1.1.1.v201101211721] is in conflict with request org.apache.commons.logging:osgi.bundle/[1.0.4.v201101211617,1.0.4.v201101211617]
[java] WARNING [0085] : Component request org.junit.source:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit.source:osgi.bundle/[4.10.0.v4_10_0_v20120426-0900,4.10.0.v4_10_0_v20120426-0900]
[java] WARNING [0036] : Component request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit:osgi.bundle/4.8.1
[java] WARNING [0036] : Component request org.junit:osgi.bundle/[3.8.2.v3_8_2_v20100427-1100,3.8.2.v3_8_2_v20100427-1100] is in conflict with request org.junit:osgi.bundle/4.7.0
[java] WARNING [0014] : Component request org.w3c.dom.smil:osgi.bundle/[1.0.0.v200806040011,1.0.0.v200806040011] is in conflict with request org.w3c.dom.smil:osgi.bundle/[1.0.1.v200903091627,1.0.1.v200903091627]
[java] ERROR [0002] : No suitable provider for component org.eclipse.emf.ecoretools.design:eclipse.feature was found in resourceMap file:/home/chakraborty/workspace/temp/maps.releng/build.rmap
[java] ERROR [0002] : No suitable provider for component org.eclipse.emf.ecoretools.design:eclipse.feature was found in searchPath eclipse
[java] ERROR [0002] : Rejecting provider p2({0}[http://download.eclipse.org/releases/juno]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/modeling/emf/updates/releases/?importType=binary[http://download.eclipse.org/modeling/emf/updates/releases/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/modeling/mdt/ocl/updates/releases/?importType=binary[http://download.eclipse.org/modeling/mdt/ocl/updates/releases/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://update.toem.de/?importType=binary[http://update.toem.de/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2(http://download.eclipse.org/birt/update-site/4.3/?importType=binary[http://download.eclipse.org/birt/update-site/4.3/?importType=binary]): No component match was found
[java] ERROR [0002] : Rejecting provider p2({0}[http://download.eclipse.org/tools/cdt/releases/8.5]): No component match was found
[java] INFO: TAG-ID 0002 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0
[java] TAG-ID 0014 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0 -> org.eclipse.e4.rcp:eclipse.feature$1.1.2.v20130130-191718-91FUvGP7GIX2Kgz-z-gvjMvXV1NS
[java] TAG-ID 0018 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0 -> org.eclipse.net4j:eclipse.feature$4.1.2.v20121028-0914
[java] TAG-ID 0036 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0 -> org.eclipse.jdt:eclipse.feature$3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83
[java] TAG-ID 0040 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0 -> org.eclipse.net4j.util:eclipse.feature$4.1.2.v20121028-0914
[java] TAG-ID 0085 = Query for maps.releng:buckminster, path: maps.releng:buckminster$1.0.0 -> org.eclipse.sdk:eclipse.feature$4.2.2.v20130116-114742-7T7oDVDQ23Iosz-vkFwNncmx7z-9Rts4b0m1FotkYacO5 -> org.eclipse.jdt.source:eclipse.feature$3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83
|
|
|
|
Powered by
FUDForum. Page generated in 0.04535 seconds
] 
Search
Help
Register
Login
Home
I also get this one: