| P2 update sites [message #118826] |
Thu, 02 October 2008 18:34  |
Eclipse User |
|
|
|
Originally posted by: fireresq.embarqmail.com
I'm looking for the documentation that describes the p2 update sites and how to set them up.
I have a collection of tools that are built on top of each other
CommonBase Feature is the base of all of the code
Tool1 Feature is the non-UI code for Tool1 and is based on CommonBase Feature
Tool1UI Feature is the UI code for Tool1 and is based on Tool1 Feature and CommonBase Feature
Tool2 Feature is the non-UI code for Tool2 and is based on CommonBase Feature
Tool2UI Feature is the UI code for Tool2 and is based on CommonBase Feature and Tool2 Feature
Tool3 Feature is the non-UI code for Tool3 and is based on CommonBase Feature, Tool1 Feature, and Tool2 Feature
Tool3UI Feature is the UI code for Tool3 and is based on CommonBase Feature and Tool3 Feature
What I'm wondering is how do I set up a P2 update site so that a user can point to the Tool3UI feature update site and have P2
find rest of the dependencies. If anyone could point me to documentation that helps me with this.
|
|
|
| Re: P2 update sites [message #118958 is a reply to message #118826] |
Sat, 04 October 2008 04:10  |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
If you want one site for all the features, I can point you to what I do
to aggregate multiple projects' updates into a single site.
http://wiki.eclipse.org/Modeling_Project_Releng/Releasing/Up date_Site_Generation
If you want p2 to be able to read across multiple sites, then AFAIK the
solution is to provide one feature which defines discovery URLs, so that
the p2 Update UI can discover those URLs, explore them, and determine
what updates are required to install Tool3 (by implicitly installing the
plugins of Tool2, Tool1, etc.
Beyond that, I suggest the wiki:
http://wiki.eclipse.org/Category:Equinox_p2
Nick
Mark Russell wrote:
> I'm looking for the documentation that describes the p2 update sites and
> how to set them up.
> I have a collection of tools that are built on top of each other
>
> CommonBase Feature is the base of all of the code
>
> Tool1 Feature is the non-UI code for Tool1 and is based on CommonBase
> Feature
> Tool1UI Feature is the UI code for Tool1 and is based on Tool1 Feature
> and CommonBase Feature
>
> Tool2 Feature is the non-UI code for Tool2 and is based on CommonBase
> Feature
> Tool2UI Feature is the UI code for Tool2 and is based on CommonBase
> Feature and Tool2 Feature
>
> Tool3 Feature is the non-UI code for Tool3 and is based on CommonBase
> Feature, Tool1 Feature, and Tool2 Feature
> Tool3UI Feature is the UI code for Tool3 and is based on CommonBase
> Feature and Tool3 Feature
>
> What I'm wondering is how do I set up a P2 update site so that a user
> can point to the Tool3UI feature update site and have P2 find rest of
> the dependencies. If anyone could point me to documentation that helps
> me with this.
>
|
|
|
| Re: P2 update sites [message #119126 is a reply to message #118958] |
Wed, 08 October 2008 15:17 |
| Eclipse User |
|
|
|
Originally posted by: fireresq.embarqmail.com
Thanks Nick. Can you point me to some documentation on how to build the discovery sites?
Nick Boldt wrote:
> If you want one site for all the features, I can point you to what I do
> to aggregate multiple projects' updates into a single site.
>
> http://wiki.eclipse.org/Modeling_Project_Releng/Releasing/Up date_Site_Generation
>
>
>
> If you want p2 to be able to read across multiple sites, then AFAIK the
> solution is to provide one feature which defines discovery URLs, so that
> the p2 Update UI can discover those URLs, explore them, and determine
> what updates are required to install Tool3 (by implicitly installing the
> plugins of Tool2, Tool1, etc.
>
> Beyond that, I suggest the wiki:
>
> http://wiki.eclipse.org/Category:Equinox_p2
>
> Nick
>
> Mark Russell wrote:
>> I'm looking for the documentation that describes the p2 update sites
>> and how to set them up.
>> I have a collection of tools that are built on top of each other
>>
>> CommonBase Feature is the base of all of the code
>>
>> Tool1 Feature is the non-UI code for Tool1 and is based on CommonBase
>> Feature
>> Tool1UI Feature is the UI code for Tool1 and is based on Tool1 Feature
>> and CommonBase Feature
>>
>> Tool2 Feature is the non-UI code for Tool2 and is based on CommonBase
>> Feature
>> Tool2UI Feature is the UI code for Tool2 and is based on CommonBase
>> Feature and Tool2 Feature
>>
>> Tool3 Feature is the non-UI code for Tool3 and is based on CommonBase
>> Feature, Tool1 Feature, and Tool2 Feature
>> Tool3UI Feature is the UI code for Tool3 and is based on CommonBase
>> Feature and Tool3 Feature
>>
>> What I'm wondering is how do I set up a P2 update site so that a user
>> can point to the Tool3UI feature update site and have P2 find rest of
>> the dependencies. If anyone could point me to documentation that
>> helps me with this.
>>
|
|
|
| Re: P2 update sites [message #119374 is a reply to message #119126] |
Sun, 12 October 2008 06:24 |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
A discovery site == an update site. Only difference is in the
feature.xml, where you either have an <update> or a <discovery>.
<url>
<update label="%EMFUpdateSiteName"
url="http://download.eclipse.org/modeling/emf/updates/"/>
<discovery label="%EMFTUpdateSiteName"
url="http://download.eclipse.org/modeling/emft/updates/"/>
</url>
Mark Russell wrote:
> Thanks Nick. Can you point me to some documentation on how to build the
> discovery sites?
>
> Nick Boldt wrote:
>> If you want one site for all the features, I can point you to what I
>> do to aggregate multiple projects' updates into a single site.
>>
>> http://wiki.eclipse.org/Modeling_Project_Releng/Releasing/Up date_Site_Generation
>>
>>
>>
>> If you want p2 to be able to read across multiple sites, then AFAIK
>> the solution is to provide one feature which defines discovery URLs,
>> so that the p2 Update UI can discover those URLs, explore them, and
>> determine what updates are required to install Tool3 (by implicitly
>> installing the plugins of Tool2, Tool1, etc.
>>
>> Beyond that, I suggest the wiki:
>>
>> http://wiki.eclipse.org/Category:Equinox_p2
>>
>> Nick
>>
>> Mark Russell wrote:
>>> I'm looking for the documentation that describes the p2 update sites
>>> and how to set them up.
>>> I have a collection of tools that are built on top of each other
>>>
>>> CommonBase Feature is the base of all of the code
>>>
>>> Tool1 Feature is the non-UI code for Tool1 and is based on CommonBase
>>> Feature
>>> Tool1UI Feature is the UI code for Tool1 and is based on Tool1
>>> Feature and CommonBase Feature
>>>
>>> Tool2 Feature is the non-UI code for Tool2 and is based on CommonBase
>>> Feature
>>> Tool2UI Feature is the UI code for Tool2 and is based on CommonBase
>>> Feature and Tool2 Feature
>>>
>>> Tool3 Feature is the non-UI code for Tool3 and is based on CommonBase
>>> Feature, Tool1 Feature, and Tool2 Feature
>>> Tool3UI Feature is the UI code for Tool3 and is based on CommonBase
>>> Feature and Tool3 Feature
>>>
>>> What I'm wondering is how do I set up a P2 update site so that a user
>>> can point to the Tool3UI feature update site and have P2 find rest of
>>> the dependencies. If anyone could point me to documentation that
>>> helps me with this.
>>>
|
|
|
| Re: P2 update sites [message #119488 is a reply to message #119374] |
Mon, 13 October 2008 19:37 |
| Eclipse User |
|
|
|
Originally posted by: fireresq.embarqmail.com
Nick, thanks for your help.
Nick Boldt wrote:
> A discovery site == an update site. Only difference is in the
> feature.xml, where you either have an <update> or a <discovery>.
>
> <url>
> <update label="%EMFUpdateSiteName"
> url="http://download.eclipse.org/modeling/emf/updates/"/>
> <discovery label="%EMFTUpdateSiteName"
> url="http://download.eclipse.org/modeling/emft/updates/"/>
> </url>
>
>
> Mark Russell wrote:
>> Thanks Nick. Can you point me to some documentation on how to build
>> the discovery sites?
>>
>> Nick Boldt wrote:
>>> If you want one site for all the features, I can point you to what I
>>> do to aggregate multiple projects' updates into a single site.
>>>
>>> http://wiki.eclipse.org/Modeling_Project_Releng/Releasing/Up date_Site_Generation
>>>
>>>
>>>
>>> If you want p2 to be able to read across multiple sites, then AFAIK
>>> the solution is to provide one feature which defines discovery URLs,
>>> so that the p2 Update UI can discover those URLs, explore them, and
>>> determine what updates are required to install Tool3 (by implicitly
>>> installing the plugins of Tool2, Tool1, etc.
>>>
>>> Beyond that, I suggest the wiki:
>>>
>>> http://wiki.eclipse.org/Category:Equinox_p2
>>>
>>> Nick
>>>
>>> Mark Russell wrote:
>>>> I'm looking for the documentation that describes the p2 update sites
>>>> and how to set them up.
>>>> I have a collection of tools that are built on top of each other
>>>>
>>>> CommonBase Feature is the base of all of the code
>>>>
>>>> Tool1 Feature is the non-UI code for Tool1 and is based on
>>>> CommonBase Feature
>>>> Tool1UI Feature is the UI code for Tool1 and is based on Tool1
>>>> Feature and CommonBase Feature
>>>>
>>>> Tool2 Feature is the non-UI code for Tool2 and is based on
>>>> CommonBase Feature
>>>> Tool2UI Feature is the UI code for Tool2 and is based on CommonBase
>>>> Feature and Tool2 Feature
>>>>
>>>> Tool3 Feature is the non-UI code for Tool3 and is based on
>>>> CommonBase Feature, Tool1 Feature, and Tool2 Feature
>>>> Tool3UI Feature is the UI code for Tool3 and is based on CommonBase
>>>> Feature and Tool3 Feature
>>>>
>>>> What I'm wondering is how do I set up a P2 update site so that a
>>>> user can point to the Tool3UI feature update site and have P2 find
>>>> rest of the dependencies. If anyone could point me to documentation
>>>> that helps me with this.
>>>>
|
|
|
Powered by
FUDForum. Page generated in 0.02471 seconds
] 
Search
Help
Register
Login
Home
