| Adding a cspex file causes import to fail [message #644382] |
Fri, 10 December 2010 13:45  |
Eclipse User |
|
|
|
I have a working Buckminster build system running through Hudson that is correctly creating a p2 repository for my feature. I would now like to have Buckminster create my product for me.
I followed these two tutorials:
http://swissdev.blogspot.com/search/label/Buckminster
http://www.ralfebert.de/blog/eclipsercp/rcp_builds/
which suggested adding a cspex file in order to add the actions create.product and create.product.zip.
As soon as I added this cspex file to the osgi bundle containing my product plugin information Buckminster started failing on import with the following error:
| Quote: |
ERROR [0002] : No suitable provider for component myproduct:osgi.bundle was found in resourceMap file:/pathToRmap/myrmap.rmap
[java] ERROR [0002] : No suitable provider for component myproduct:osgi.bundle was found in searchPath mySearchPath
[java] ERROR [0002] : Resolution attempt ended with exception: CSpec myproduct:osgi.bundle$1.0.0.qualifier has no action, group, or local artifact named site.p2
[java] ERROR CSpec myproduct:osgi.bundle$1.0.0.qualifier has no action, group, or local artifact named site.p2
[java] myproduct:osgi.bundle: Resolution attempt ended with exception: CSpec myproduct:osgi.bundle$1.0.0.qualifier has no action, group, or local artifact named site.p2
|
I know the cspex is causing this error because when I rename the cspex (to something like buckminster.cspex.off) then my build executes properly.
Here is the contents of the cspex file:
<?xml version="1.0" encoding="UTF-8"?>
<cspecExtension xmlns:com="http://www.eclipse.org/buckminster/Common-1.0"
xmlns="http://www.eclipse.org/buckminster/CSpec-1.0">
<actions>
<public name="create.product" actor="ant">
<actorProperties>
<property key="buildFile" value="build/product.ant" />
<property key="targets" value="create.product" />
</actorProperties>
<properties>
<property key="profile" value="Juice" />
<property key="iu" value="com.cmcflex.juice" />
</properties>
<prerequisites alias="repository">
<attribute name="site.p2" />
</prerequisites>
<products alias="destination" base="${buckminster.output}">
<path path="mail.${target.ws}.${target.os}.${target.arch}/" />
</products>
</public>
<public name="create.product.zip" actor="ant">
<actorProperties>
<property key="buildFileId" value="buckminster.pdetasks" />
<property key="targets" value="create.zip" />
</actorProperties>
<prerequisites alias="action.requirements">
<attribute name="create.product" />
</prerequisites>
<products alias="action.output" base="${buckminster.output}">
<path path="mail.${target.ws}.${target.os}.${target.arch}.zip" />
</products>
</public>
</actions>
</cspecExtension> |
|
|
|
| Re: Adding a cspex file causes import to fail [message #644680 is a reply to message #644436] |
Mon, 13 December 2010 13:29  |
| Eclipse User |
|
|
|
| Thorsten Meinl wrote on Sat, 11 December 2010 03:36 | Am 10.12.2010 19:45, schrieb Philip Borlin:
You need to add the cspex to the feature containing your update site
|
When I move the cspex file to my feature I am now getting told there is no buckminster.clean action.
| Quote: |
...
ERROR [0001] : Resolution attempt ended with exception: CSpec myfeature has no action, group, or local artifact named buckminster.clean
...
|
The interesting thing is that when I generate a cspec in Eclipse by right clicking on my feature project, selecting Buckminster, and then selecting View CSpec... the clean action shows up.
When I refresh my feature project from within Eclipse it shows an error in the console:
| Quote: |
Project refresh on com.cmcflex.juice.feature failed: CSpec com.cmcflex.juice.feature has no action, group, or local artifact named buckminster.clean
|
Even more interesting is the fact that with the cspex file in the bundle that contains my product (the original approach), the cspec file produced by Eclipse contains the site.p2 action and refreshing the project gives no errors.
Thanks for your help.
|
|
|
|
| Re: Adding a cspex file causes import to fail [message #646423 is a reply to message #645208] |
Thu, 23 December 2010 19:03 |
| Eclipse User |
|
|
|
| Philip Borlin wrote on Wed, 15 December 2010 17:45 | I solved the problem - it ended up being a problem with one of my feature.xml files. I was referencing some bundle that did not belong in my product and once I took that bundle out of the feature it started working.
|
I just hit this issue as well. It would be good to be able to get a message about what bundles are at issue instead of this opaque failure..
|
|
|
Powered by
FUDForum. Page generated in 0.03883 seconds
Home