Home » Eclipse Projects » P2 » Give me some references or advice about how to build and publish a p2 update site(How to build and publish a p2 update site)
|
| Re: Give me some references or advice about how to build and publish a p2 update site [message #1229849 is a reply to message #1215936] |
Fri, 10 January 2014 11:04   |
 Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
On 28-11-13 09:55, Lee Cheng wrote:
> I have to build and publish a p2 site for updating plugins of our ide
> product based on Eclipse v4.But I cannot find how to implement it.
>
> I exported the product by "Eclipse Product export wizard" with checking
> "Generate p2 repository" item on product file page. After the
> exporting, I move the generated repository directory into a web server,
> open the menu Help > Install New Software, and add the web site into
> "Available Software Sites", but the response is "There is no categorized
> items"
I don't know how your p2 looks like, but when you export a p2, there
should be a file named category.xml which tells how the features are
grouped in the p2 repo. (You can do file -> new -> pde -> Category
Definition). Although I don't know how the product exporter will use
this file though, I use it in a different way (read-on!).
There is also a checkbox in the installer, which says: "Group Items by
category", if you turn it off, you should see your features. (If your
product is feature based, as products can be plugin/feature based).
Another way to produce a P2 is to do file -> export -> Deployable
features. In the Options tab, you can specify a category.xml file.
The downside here, is that you already specifed all your features in the
..product, and will need to repeat re-specify your features which consist
your product. If your product is only to install plugins in an IDE, this
option is workable.
Finally, you can also produce old-style update site, with file -> new ->
PDE -> Update Site Project, but you might not want to use this...(It's
not P2).
Note that the PDE p2 tooling is very limited, I prefer to use the
headless P2 publisher, (Which is also used by build tools like
Buckminster or Tycho). You really tweak exactly as you want it.
http://wiki.eclipse.org/Equinox/p2/Publisher
Does this help?
Cheers / Christophe
>
> I can not understand content.xml file and artifact.xml file structure.
> I've searched on eclipse.org, and only found the expired version info on
> http://wiki.eclipse.org/Equinox_p2_Metadata_Authoring.
>
> Who can help me?
>
> Best regards
|
|
|
| Re: Give me some references or advice about how to build and publish a p2 update site [message #1229852 is a reply to message #1229849] |
Fri, 10 January 2014 11:07 |
Christophe Bouhier
Messages: 937
Registered: July 2009 |
Senior Member |
|
|
You can actually add your categories with this tool:
http://wiki.eclipse.org/Equinox/p2/Publisher#Category_Publisher
On 10-01-14 12:04, Christophe Bouhier wrote:
> On 28-11-13 09:55, Lee Cheng wrote:
>> I have to build and publish a p2 site for updating plugins of our ide
>> product based on Eclipse v4.But I cannot find how to implement it.
>>
>> I exported the product by "Eclipse Product export wizard" with checking
>> "Generate p2 repository" item on product file page. After the
>> exporting, I move the generated repository directory into a web server,
>> open the menu Help > Install New Software, and add the web site into
>> "Available Software Sites", but the response is "There is no categorized
>> items"
> I don't know how your p2 looks like, but when you export a p2, there
> should be a file named category.xml which tells how the features are
> grouped in the p2 repo. (You can do file -> new -> pde -> Category
> Definition). Although I don't know how the product exporter will use
> this file though, I use it in a different way (read-on!).
>
> There is also a checkbox in the installer, which says: "Group Items by
> category", if you turn it off, you should see your features. (If your
> product is feature based, as products can be plugin/feature based).
>
> Another way to produce a P2 is to do file -> export -> Deployable
> features. In the Options tab, you can specify a category.xml file.
> The downside here, is that you already specifed all your features in the
> .product, and will need to repeat re-specify your features which consist
> your product. If your product is only to install plugins in an IDE, this
> option is workable.
>
> Finally, you can also produce old-style update site, with file -> new ->
> PDE -> Update Site Project, but you might not want to use this...(It's
> not P2).
>
> Note that the PDE p2 tooling is very limited, I prefer to use the
> headless P2 publisher, (Which is also used by build tools like
> Buckminster or Tycho). You really tweak exactly as you want it.
>
> http://wiki.eclipse.org/Equinox/p2/Publisher
>
>
> Does this help?
> Cheers / Christophe
>
>
>
>
>
>
>
>
>>
>> I can not understand content.xml file and artifact.xml file structure.
>> I've searched on eclipse.org, and only found the expired version info on
>> http://wiki.eclipse.org/Equinox_p2_Metadata_Authoring.
>>
>> Who can help me?
>>
>> Best regards
>
|
|
|
Goto Forum:
Current Time: Wed Apr 24 23:22:48 GMT 2024
Powered by FUDForum. Page generated in 0.02853 seconds |
] 
Search
Help
Register
Login
Home
