|
| Re: populate target platform [message #522349 is a reply to message #522327] |
Mon, 22 March 2010 13:14   |
|
Hi Alain,
Your feature holds references to other features and/or plugins. Where do they reside in relation to the feature? Are
they available on an update site (legacy or p2) ?
- thomas
On 03/22/2010 12:25 PM, Alain Helfenstein wrote:
> Hi
>
> I use a buckminster headless "import" command (pointing to a mspec) in
> order to populate my target platform.
>
> Now I want to add a prebuild 3rd party feature to my target platform.
>
> How do I do that?
>
>
> I tried several approaches whitout success:
>
> 1. add the 3rd party feature to the rmap that will be used by the mspec
> while the "import" is taking place. But I couldn't figure out, how to
> add a provider to the rmap for a prebuild 3rd party feature
>
> 2. I try to add a second "import" command, but you can only reference to
> mspec files. But how to make a mspec if I only have the prebuild feature
> in a zip file? - Without p2 update site?
>
> Any ideas?
>
> Kind regards, Alain.
|
|
|
|
| Re: populate target platform [message #522395 is a reply to message #522355] |
Mon, 22 March 2010 14:34 |
|
The simplest fix for that is then probably to add a site.xml file so that you get a legacy style update site, i.e.
albireo/site.xml
albireo/features
albireo/plugins
and then use the 'p2' reader type (or 'eclipse.import' in 3.5) in conjunction with URL using the file protocol.
HTH,
- thomas
On 03/22/2010 02:24 PM, Alain Helfenstein wrote:
> Hi Thomas
>
> Thanks for your answer.
> No, they are not available on a update site.
> They just resides on my harddisk as a folder with the following structure:
>
> albireo/features
> albireo/plugins
>
> Regards, Alain.
>
>
> Thomas Hallgren schrieb:
>> Hi Alain,
>> Your feature holds references to other features and/or plugins. Where
>> do they reside in relation to the feature? Are they available on an
>> update site (legacy or p2) ?
>>
>> - thomas
>>
>>
>> On 03/22/2010 12:25 PM, Alain Helfenstein wrote:
>>> Hi
>>>
>>> I use a buckminster headless "import" command (pointing to a mspec) in
>>> order to populate my target platform.
>>>
>>> Now I want to add a prebuild 3rd party feature to my target platform.
>>>
>>> How do I do that?
>>>
>>>
>>> I tried several approaches whitout success:
>>>
>>> 1. add the 3rd party feature to the rmap that will be used by the mspec
>>> while the "import" is taking place. But I couldn't figure out, how to
>>> add a provider to the rmap for a prebuild 3rd party feature
>>>
>>> 2. I try to add a second "import" command, but you can only reference to
>>> mspec files. But how to make a mspec if I only have the prebuild feature
>>> in a zip file? - Without p2 update site?
>>>
>>> Any ideas?
>>>
>>> Kind regards, Alain.
>>
|
|
|
| Re: populate target platform [message #524599 is a reply to message #522395] |
Thu, 01 April 2010 14:47 |
 Alain 
Messages: 115
Registered: July 2009 |
Senior Member |
|
|
Hi Thomas
It worked on my local machine whitout any problems. I think the site.xml
is even not needen.
But on the build server I get the following error (havin the site.xml in
the folder):
ERROR [0002] : Unable to resolve Installable Unit
org.eclipse.albireo.core 0.0.3.v20081031 in repository
file:///D:/test/test/data/albireo
ERROR: Unable to resolve Installable Unit org.eclipse.albireo.core
0.0.3.v20081031 in repository file:///D:/test/test/data/albireo
ERROR: Errors and Warnings
org.eclipse.core.runtime.CoreException: Errors and Warnings
at
org.eclipse.buckminster.runtime.BuckminsterException.wrap(Bu ckminsterException.java:109)
at
org.eclipse.buckminster.core.materializer.MaterializationJob .internalRun(MaterializationJob.java:175)
at
org.eclipse.buckminster.core.materializer.MaterializationJob .run(MaterializationJob.java:144)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Contains: [0002] : Unable to resolve Installable Unit
org.eclipse.albireo.core 0.0.3.v20081031 in repository
file:///D:/test/test/data/albireo
The file really exists, because if I remove the file, then another error
message will be displayed.
The rmap looks like this:
<searchPath name="albireo">
<provider readerType="eclipse.import"
componentTypes="osgi.bundle,eclipse.feature" mutable="false" source="false">
<uri format="file:///D:/test/test/data/albireo"/>
</provider>
</searchPath>
And the site.xml looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<site>
<feature url="features/org.eclipse.albireo_0.0.3.v20081031.jar"
id="org.eclipse.albireo" version="0.0.3.v20081031">
<category name="albireo"/>
</feature>
<feature url="features/org.eclipse.albireo.sdk_0.0.3.v20081031.jar"
id="org.eclipse.albireo.sdk" version="0.0.3.v20081031">
<category name="albireo"/>
</feature>
<feature
url="features/org.eclipse.albireo.source_0.0.3.v20081031.jar "
id="org.eclipse.albireo.source" version="0.0.3.v20081031">
<category name="albireo"/>
</feature>
<category-def name="albireo" label="albireo">
<description>
albireo
</description>
</category-def>
</site>
Any idea about this?
Thanks a lot for your help, Alain.
Thomas Hallgren schrieb:
> The simplest fix for that is then probably to add a site.xml file so
> that you get a legacy style update site, i.e.
>
> albireo/site.xml
> albireo/features
> albireo/plugins
>
> and then use the 'p2' reader type (or 'eclipse.import' in 3.5) in
> conjunction with URL using the file protocol.
>
> HTH,
> - thomas
>
>
> On 03/22/2010 02:24 PM, Alain Helfenstein wrote:
>> Hi Thomas
>>
>> Thanks for your answer.
>> No, they are not available on a update site.
>> They just resides on my harddisk as a folder with the following
>> structure:
>>
>> albireo/features
>> albireo/plugins
>>
>> Regards, Alain.
>>
>>
>> Thomas Hallgren schrieb:
>>> Hi Alain,
>>> Your feature holds references to other features and/or plugins. Where
>>> do they reside in relation to the feature? Are they available on an
>>> update site (legacy or p2) ?
>>>
>>> - thomas
>>>
>>>
>>> On 03/22/2010 12:25 PM, Alain Helfenstein wrote:
>>>> Hi
>>>>
>>>> I use a buckminster headless "import" command (pointing to a mspec) in
>>>> order to populate my target platform.
>>>>
>>>> Now I want to add a prebuild 3rd party feature to my target platform.
>>>>
>>>> How do I do that?
>>>>
>>>>
>>>> I tried several approaches whitout success:
>>>>
>>>> 1. add the 3rd party feature to the rmap that will be used by the mspec
>>>> while the "import" is taking place. But I couldn't figure out, how to
>>>> add a provider to the rmap for a prebuild 3rd party feature
>>>>
>>>> 2. I try to add a second "import" command, but you can only
>>>> reference to
>>>> mspec files. But how to make a mspec if I only have the prebuild
>>>> feature
>>>> in a zip file? - Without p2 update site?
>>>>
>>>> Any ideas?
>>>>
>>>> Kind regards, Alain.
>>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03079 seconds
] 
Search
Help
Register
Login
Home
