Eclipse Community Forums: Buckminster » Unpredictable resolution failures using remote PDE map files

Help

Home

Home » Archived » Buckminster » Unpredictable resolution failures using remote PDE map files

Show: Today's Messages :: Show Polls :: Message Navigator

Unpredictable resolution failures using remote PDE map files [message #381327]

Wed, 26 November 2008 17:24

Oisin Hurley

Messages: 204
Registered: July 2009

Senior Member

I've got an RMAP that has two searchPaths using PDE .map files

<searchPath name="my-stuff">
<provider readerType="eclipse.import" componentTypes="osgi.bundle"
mutable="false" source="false">
<uri
format="http://myHost/eclipse/updates/my-stuff/my-stuff.pluginmap" />
</provider>
</searchPath>

<searchPath name="orbit-stuff">
<provider readerType="eclipse.import" componentTypes="osgi.bundle"
mutable="false" source="false">
<uri
format=" http://myHost/eclipse/updates/orbit-stuff/orbit-stuff.plugin map" />
</provider>
</searchPath>

I see failures in resolution, randomly from one searchPath provider or the
other, for bundles referenced from the PDE map files.

I've done a build with maxParallelResolutions=1, but the resolutions still
fail with
the "No Suitable Provider for component x.y.z:osgi:bundle was found in
searchpath my-stuff"
message. On a manual check, x.y.z is in the .pluginmap file, and x.y.z.jar
is available using
a standard wget.

(I've renamed the .map files to .pluginmap, because for some reason the
map extension
makes the webserver spew. Could this be important?)

Before I go to the next step and dig into the code, has anyone seen this
kind
of behaviour before?

cheers
--oh

Report message to a moderator

Re: Unpredictable resolution failures using remote PDE map files [message #381328 is a reply to message #381327]

Wed, 26 November 2008 17:26

Oisin Hurley

Messages: 204
Registered: July 2009

Senior Member

Apologies, forgot to mention: I'm using headless buil here, version
1.1.0.r09505, and Eclipse 3.4.1

--oh

Report message to a moderator

Re: Unpredictable resolution failures using remote PDE map files [message #381330 is a reply to message #381327]

Thu, 27 November 2008 07:22

Thomas Hallgren

Messages: 3240
Registered: July 2009

Senior Member

Hi Oisin,

Oisin Hurley wrote:
> (I've renamed the .map files to .pluginmap, because for some reason the
> map extension
> makes the webserver spew. Could this be important?)
>
Yes, most definitely. I'm surprised that your errors are random. The import reader
triggers on entries that ends with ".map". Only such entries are considered to be maps so
an extension of ".pluginmap" should fail completely. What errors do you see? Could it be
that the components are resolved using another provider/searchPath?

Regards,
Thomas Hallgren

Report message to a moderator

Re: Unpredictable resolution failures using remote PDE map files [message #381340 is a reply to message #381330]

Sun, 30 November 2008 23:23

Oisin Hurley

Messages: 204
Registered: July 2009

Senior Member

Thomas Hallgren wrote:
> Yes, most definitely. I'm surprised that your errors are random. The import
reader
> triggers on entries that ends with ".map". Only such entries are considered
to be maps so
> an extension of ".pluginmap" should fail completely. What errors do you see?
Could it be
> that the components are resolved using another provider/searchPath?

I neglected to reply to the newsgroup about this one - my apologies. The main
issue was the irregular file suffix. Once I had made sure that the PDE map
files were indeed .map, and web server had been prevented from trying to
interpret them as imagemaps, then resolution started to occur as expected :)

--oh

----
oisin hurley at iona
http://oisinh.wordpress.com

Report message to a moderator

Previous Topic:	How to point BM to a materialized target platform
Next Topic:	Import-Package and feature requirements

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 00:26:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter