Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Buckminster » Possibly odd RMAP question
Possibly odd RMAP question [message #649494] Wed, 19 January 2011 13:23 Go to next message
Jesper Eskilson is currently offline Jesper EskilsonFriend
Messages: 134
Registered: July 2009
Senior Member
I'm trying to write a RMAP provider for a certain type of component, but
can't seem to get it all right.

I have a plugin A containing only documentation (i.e. no Java-code). The
plugin is delivered in the form of a jar-file. If I unpack the jar, I
can resolve it using the same way as I resolve everything all other plugins:

<rm:provider componentTypes="osgi.bundle"
readerType="url.catalog" source="false" resolutionFilter="">
<rm:uri format="{0}/plugins/{1}">
<bc:propertyRef key="hubble.root.url"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>

Now, I would like to avoid having to unpack the jar, and instead get the
RMAP to resolve the plugin directly. If I try to just edit the "uri"
field like this:

<rm:searchPath name="docjars">
<rm:provider componentTypes="osgi.bundle" readerType="url.catalog"
source="false" resolutionFilter="">
<rm:uri format="{0}/docjars/{1}.jar">
^^^^^^^^
<bc:propertyRef key="hubble.root.url"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider>
</rm:searchPath>

but then Buckminster complains with the following error:

[java] ERROR [0002] : Resolution attempt ended with
exception: Provider
url.catalog(file:/home/jesperes/dev/eclipse//docjars/com.web works.eclipsehelp.Eclipsetest.jar):
Missing CSpec source required by component type osgi.bundle

Is it possible to do this?

--
Jesper Eskilson
Developer
IAR Systems
Re: Possibly odd RMAP question [message #649591 is a reply to message #649494] Wed, 19 January 2011 20:22 Go to previous messageGo to next message
Alex Kravets is currently offline Alex KravetsFriend
Messages: 561
Registered: November 2009
Senior Member
Instead of specifically adding jar to your uri as in:
<rm:uri format="{0}/docjars/{1}.jar">

Have you tried adding jar to the list of component types? Because since you specify your component type as osgi.bundle and jar is found, there is a mismatch. You can also append "jar" to your existing component types and it will match both:

<rm:provider componentTypes="osgi.bundle,jar"
readerType="url.catalog" source="false" resolutionFilter="">
<rm:uri format="{0}/plugins/{1}">
<bc:propertyRef key="hubble.root.url"/>
<bc:propertyRef key="buckminster.component"/>
</rm:uri>
</rm:provider


Regards,
Alex
Re: Possibly odd RMAP question [message #649677 is a reply to message #649591] Thu, 20 January 2011 09:17 Go to previous message
Jesper Eskilson is currently offline Jesper EskilsonFriend
Messages: 134
Registered: July 2009
Senior Member
On 01/19/2011 09:22 PM, Alex wrote:
> Instead of specifically adding jar to your uri as in:
>
> <rm:uri format="{0}/docjars/{1}.jar">
>
> Have you tried adding jar to the list of component types? Because since
> you specify your component type as osgi.bundle and jar is found, there
> is a mismatch. You can also append "jar" to your existing component
> types and it will match both:
>
>
> <rm:provider componentTypes="osgi.bundle,jar"
> readerType="url.catalog" source="false" resolutionFilter="">
> <rm:uri format="{0}/plugins/{1}">
> <bc:propertyRef key="hubble.root.url"/>
> <bc:propertyRef key="buckminster.component"/>
> </rm:uri>
> </rm:provider

No difference. I still get the "Missing CSpec source required by
component type osgi.bundle", which to me looks like it actually finds
the plugin, but is unable to generate the cspec directly from the jar.

--
Jesper Eskilson
Developer
IAR Systems
Previous Topic:site signing asks for keystore passphrase
Next Topic:RMAP issue with prebuilt plugins (attempt 2)
Goto Forum:
  


Current Time: Tue Apr 16 14:56:54 GMT 2024

Powered by FUDForum. Page generated in 0.32840 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top