| Changes/Regression with BM > rev 09937 [message #383213] |
Wed, 11 March 2009 08:36  |
Eclipse User |
|
|
|
Originally posted by: news.eclipse.org.08.lemmster.de
Hi,
with the recent build 09951 from updates-3.5/, BM fails to resolve three
ECF bundles. This does not happen with a build based on 9937. Has
anything changed or is this a regression?
Thanks
Markus
ERROR : No suitable provider for component
ch.ethz.iks.r_osgi.remote:osgi.bundle was found in searchPath
org.eclipse.ecf
ERROR : Resolution attempt ended with exception:
CSpec ch.ethz.iks.r_osgi.remote:osgi.bundle$1.0.0.RC4_qualifier#OS Gi has
no action, group, or local artifact named source.manifest
ERROR : No suitable provider for component
org.jivesoftware.smack:osgi.bundle was found in searchPath org.eclipse.ecf
ERROR : Resolution attempt ended with exception:
CSpec org.jivesoftware.smack:osgi.bundle$2.2.1#OSGi has no action,
group, or local artifact named source.manifest
ERROR : No suitable provider for component
org.eclipse.ecf.osgi.services:osgi.bundle was found in searchPath
org.eclipse.ecf
ERROR : Resolution attempt ended with exception:
CSpec org.eclipse.ecf.osgi.services:osgi.bundle$4.2.0.200902130831 #OSGi
has no action, group, or local artifact named source.manifest
ERROR : No suitable provider for component
ch.ethz.iks.r_osgi.remote:osgi.bundle was found in searchPath
org.eclipse.ecf
ERROR : Resolution attempt ended with exception:
CSpec ch.ethz.iks.r_osgi.remote:osgi.bundle$1.0.0.RC4_qualifier#OS Gi has
no action, group, or local artifact named source.manifest
ERROR : No suitable provider for component
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi was found in
searchPath org.eclipse.ecf
ERROR : Resolution attempt ended with exception:
CSpec org.jivesoftware.smack:osgi.bundle$2.2.1#OSGi has no action,
group, or local artifact named source.manifest
ERROR: Attempt to use an unresolved node. Request is
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
org.eclipse.buckminster.core.metadata.model.UnresolvedNodeEx ception:
Attempt to use an unresolved node. Request is
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
at
org.eclipse.buckminster.core.metadata.model.UnresolvedNode.a ddMaterializationCandidates(UnresolvedNode.java:51)
at
org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
at
org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
at
org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
at
org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
at
org.eclipse.buckminster.core.metadata.model.BillOfMaterials. addMaterializationCandidates(BillOfMaterials.java:187)
at
org.eclipse.buckminster.core.metadata.model.BillOfMaterials. findMaterializationCandidates(BillOfMaterials.java:228)
at
org.eclipse.buckminster.core.materializer.MaterializationJob .prepareJobs(MaterializationJob.java:180)
at
org.eclipse.buckminster.core.materializer.MaterializationJob .internalRun(MaterializationJob.java:152)
at
org.eclipse.buckminster.core.materializer.MaterializationJob .run(MaterializationJob.java:220)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
ERROR: Attempt to use an unresolved node. Request is
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
org.eclipse.core.runtime.CoreException: Attempt to use an
unresolved node. Request is
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
[java] at
org.eclipse.buckminster.core.materializer.MaterializationJob .run(MaterializationJob.java:70)
[java] at
org.eclipse.buckminster.core.commands.Import.internalRun(Imp ort.java:226)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceInitCommand.i nternalRun(WorkspaceInitCommand.java:160)
[java] at
org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
[java] at
org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 95)
[java] at
org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 29)
[java] at
org.eclipse.buckminster.cmdline.Headless.start(Headless.java :304)
[java] at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
[java] at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
[java] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 556)
[java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
[java] at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
[java] at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
[java] at org.eclipse.core.launcher.Main.main(Main.java:30)
[java] Attempt to use an unresolved node. Request is
org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
|
|
|
| Re: Changes/Regression with BM > rev 09937 [message #383214 is a reply to message #383213] |
Wed, 11 March 2009 08:41  |
|
From the looks of it, Buckminster encounters old meta-data. Did you try
refreshing the meta-data or using a new workspace?
Regards,
Thomas Hallgren
Markus Kuppe wrote:
> Hi,
>
> with the recent build 09951 from updates-3.5/, BM fails to resolve three
> ECF bundles. This does not happen with a build based on 9937. Has
> anything changed or is this a regression?
>
> Thanks
> Markus
>
> ERROR : No suitable provider for component
> ch.ethz.iks.r_osgi.remote:osgi.bundle was found in searchPath
> org.eclipse.ecf
> ERROR : Resolution attempt ended with exception:
> CSpec ch.ethz.iks.r_osgi.remote:osgi.bundle$1.0.0.RC4_qualifier#OS Gi has
> no action, group, or local artifact named source.manifest
> ERROR : No suitable provider for component
> org.jivesoftware.smack:osgi.bundle was found in searchPath org.eclipse.ecf
> ERROR : Resolution attempt ended with exception:
> CSpec org.jivesoftware.smack:osgi.bundle$2.2.1#OSGi has no action,
> group, or local artifact named source.manifest
> ERROR : No suitable provider for component
> org.eclipse.ecf.osgi.services:osgi.bundle was found in searchPath
> org.eclipse.ecf
> ERROR : Resolution attempt ended with exception:
> CSpec org.eclipse.ecf.osgi.services:osgi.bundle$4.2.0.200902130831 #OSGi
> has no action, group, or local artifact named source.manifest
> ERROR : No suitable provider for component
> ch.ethz.iks.r_osgi.remote:osgi.bundle was found in searchPath
> org.eclipse.ecf
> ERROR : Resolution attempt ended with exception:
> CSpec ch.ethz.iks.r_osgi.remote:osgi.bundle$1.0.0.RC4_qualifier#OS Gi has
> no action, group, or local artifact named source.manifest
> ERROR : No suitable provider for component
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi was found in
> searchPath org.eclipse.ecf
> ERROR : Resolution attempt ended with exception:
> CSpec org.jivesoftware.smack:osgi.bundle$2.2.1#OSGi has no action,
> group, or local artifact named source.manifest
> ERROR: Attempt to use an unresolved node. Request is
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
>
> org.eclipse.buckminster.core.metadata.model.UnresolvedNodeEx ception:
> Attempt to use an unresolved node. Request is
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
> at
> org.eclipse.buckminster.core.metadata.model.UnresolvedNode.a ddMaterializationCandidates(UnresolvedNode.java:51)
> at
> org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
> at
> org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
> at
> org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
> at
> org.eclipse.buckminster.core.metadata.model.ResolvedNode.add MaterializationCandidates(ResolvedNode.java:125)
> at
> org.eclipse.buckminster.core.metadata.model.BillOfMaterials. addMaterializationCandidates(BillOfMaterials.java:187)
> at
> org.eclipse.buckminster.core.metadata.model.BillOfMaterials. findMaterializationCandidates(BillOfMaterials.java:228)
> at
> org.eclipse.buckminster.core.materializer.MaterializationJob .prepareJobs(MaterializationJob.java:180)
> at
> org.eclipse.buckminster.core.materializer.MaterializationJob .internalRun(MaterializationJob.java:152)
> at
> org.eclipse.buckminster.core.materializer.MaterializationJob .run(MaterializationJob.java:220)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> ERROR: Attempt to use an unresolved node. Request is
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
> org.eclipse.core.runtime.CoreException: Attempt to use an
> unresolved node. Request is
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
> [java] at
> org.eclipse.buckminster.core.materializer.MaterializationJob .run(MaterializationJob.java:70)
> [java] at
> org.eclipse.buckminster.core.commands.Import.internalRun(Imp ort.java:226)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceInitCommand.i nternalRun(WorkspaceInitCommand.java:160)
> [java] at
> org.eclipse.buckminster.core.commands.WorkspaceCommand.run(W orkspaceCommand.java:99)
> [java] at
> org.eclipse.buckminster.cmdline.AbstractCommand.basicRun(Abs tractCommand.java:155)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 95)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.run(Headless.java:2 29)
> [java] at
> org.eclipse.buckminster.cmdline.Headless.start(Headless.java :304)
> [java] at
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(Eclips eAppHandle.java:194)
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:110)
> [java] at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:79)
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:368)
> [java] at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:179)
> [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [java] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
> [java] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
> [java] at java.lang.reflect.Method.invoke(Method.java:597)
> [java] at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 556)
> [java] at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511)
> [java] at org.eclipse.equinox.launcher.Main.run(Main.java:1284)
> [java] at org.eclipse.equinox.launcher.Main.main(Main.java:1260)
> [java] at org.eclipse.core.launcher.Main.main(Main.java:30)
> [java] Attempt to use an unresolved node. Request is
> org.jivesoftware.smack:osgi.bundle/[2.2.1,3.0.0)#OSGi
|
|
|
| Re: Changes/Regression with BM > rev 09937 [message #383215 is a reply to message #383214] |
Wed, 11 March 2009 09:07 |
| Eclipse User |
|
|
|
Originally posted by: news.eclipse.org.08.lemmster.de
Thomas Hallgren wrote:
> From the looks of it, Buckminster encounters old meta-data. Did you try
> refreshing the meta-data or using a new workspace?
>
> Regards,
> Thomas Hallgren
Nope, same error. Even with a fresh workspace, .metadata, .configuration
and cleaned .buckminster repo.
Thanks
Markus
|
|
|
| Re: Changes/Regression with BM > rev 09937 [message #383216 is a reply to message #383215] |
Wed, 11 March 2009 10:01 |
|
OK. I suggest you stay with 9937 for now then. I'm in the middle of
changing the site publishing and the way we create and manage the
Buckminster headless product and the trunk is not stable enough for a
new release just yet. The changes are necessary for us in order to get
rid of hard dependencies on the now deprecated old Update Manager.
- thomas
Markus Kuppe wrote:
> Thomas Hallgren wrote:
>> From the looks of it, Buckminster encounters old meta-data. Did you try
>> refreshing the meta-data or using a new workspace?
>>
>> Regards,
>> Thomas Hallgren
>
> Nope, same error. Even with a fresh workspace, .metadata, .configuration
> and cleaned .buckminster repo.
>
> Thanks
> Markus
|
|
|
Powered by
FUDForum. Page generated in 0.02740 seconds
] 
Search
Help
Register
Login
Home
