|
|
|
| Re: Dump p2 URLs [message #672050 is a reply to message #672044] |
Thu, 19 May 2011 17:24   |
 Carsten Reckord
Messages: 139
Registered: July 2009 |
Senior Member |
|
|
Hi Eike,
Yes, sadly the provider nodes are not expanded. But the resolution nodes
contain the fully expanded repository location in the "repository"
attribute, as well as a pointer to their provider to discern its type in
case the resolution's componentType=osgi.bundle/eclipse.feature is not
enough to distinguish between p2 and other sources.
On 19.05.2011 18:50, Eike Stepper wrote:
> Am 19.05.2011 15:04, schrieb Carsten Reckord:
>> Hi Eike,
>>
>> You could save the BOM during materialization. It contains all resolution
>> results including the p2 repositories. Extracting the repositories should be
>> fairly simple with XSL or even sed. To save the BOM use "Save BOM" on the
>> resolution page of the Buckminster Import Wizard or with the CLI use import
>> -B<filename>.
> Unfortunately the bom contains the needed rmap info in the same way as the rmap itself, i.e. property references are not resolved/substituted ;-(
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>> HTH,
>> Carsten
>>
>> On 19.05.2011 12:25, Eike Stepper wrote:
>>> Hi,
>>>
>>> Is there a way to make bucky spit out a list of the used p2 repositories during a provision action? The background is that I would like to generate a p2 bookmark.xml file that can be used to initialize a p2 client with a build's prerequisite locations.
>>>
>>> Cheers
>>> /Eike
>>>
>>> ----
>>> http://www.esc-net.de
>>> http://thegordian.blogspot.com
>>> http://twitter.com/eikestepper
>>>
>>>
|
|
|
| Re: Dump p2 URLs [message #673982 is a reply to message #672050] |
Wed, 25 May 2011 11:26 |
|
Thank you, Carsten!
It took a while and some failed builds but now we can produce an importable bookmarks.xml: https://hudson.eclipse.org/hudson/job/emf-cdo-integration/lastSuccessfulBuild/artifact/result/site.p2/bookmarks.xml
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 19.05.2011 19:24, schrieb Carsten Reckord:
> Hi Eike,
>
> Yes, sadly the provider nodes are not expanded. But the resolution nodes
> contain the fully expanded repository location in the "repository"
> attribute, as well as a pointer to their provider to discern its type in
> case the resolution's componentType=osgi.bundle/eclipse.feature is not
> enough to distinguish between p2 and other sources.
>
> On 19.05.2011 18:50, Eike Stepper wrote:
>> Am 19.05.2011 15:04, schrieb Carsten Reckord:
>>> Hi Eike,
>>>
>>> You could save the BOM during materialization. It contains all resolution
>>> results including the p2 repositories. Extracting the repositories should be
>>> fairly simple with XSL or even sed. To save the BOM use "Save BOM" on the
>>> resolution page of the Buckminster Import Wizard or with the CLI use import
>>> -B<filename>.
>> Unfortunately the bom contains the needed rmap info in the same way as the rmap itself, i.e. property references are not resolved/substituted ;-(
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>>> HTH,
>>> Carsten
>>>
>>> On 19.05.2011 12:25, Eike Stepper wrote:
>>>> Hi,
>>>>
>>>> Is there a way to make bucky spit out a list of the used p2 repositories during a provision action? The background is that I would like to generate a p2 bookmark.xml file that can be used to initialize a p2 client with a build's prerequisite locations.
>>>>
>>>> Cheers
>>>> /Eike
>>>>
>>>> ----
>>>> http://www.esc-net.de
>>>> http://thegordian.blogspot.com
>>>> http://twitter.com/eikestepper
>>>>
>>>>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.03336 seconds
] 
Search
Help
Register
Login
Home
