My question actually is how you are going to install 3.6.1 on top of the existing 3.6.0. For instance, 3.6.0 contains 30 plugins and 2 of them have been updated in 3.6.1. You don't want the end user to pick up a 3.6.1 zip file and unzip it again.
Best Regards Samuel Wu |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |"Yousouf, Shenol" <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |P2 developer discussions <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |09/08/2010 03:19 AM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [p2-dev] How to build an update site for a product? | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Sent by: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |[email protected] | >--------------------------------------------------------------------------------------------------------------------------------------------------| Hello Samuel, I am sorry if I do not grasp some of the details in your use case so you may already be familiar with the information that follows. If you lack a product IU in the repository that gathers all the features/plugins you need, the usual way is to describe them in a .product file and publish it into the site you already have. You can automate the publishing process in an ant build by using the respective p2 ant tasks for that purpose. You can find further details about the various publisher applications on the following page: http://wiki.eclipse.org/Equinox/p2/Publisher If you need to publish a new release of your product, just increment the version attribute of the .product file. The generated product IU will hold the necessary update metadata to signify that it replaces the older releases during install. Hope this helps ! Best regards, Shenol Yousouf SAP Labs Bulgaria From: [email protected] [mailto:[email protected]] On Behalf Of Samuel Wu Sent: Wednesday, September 08, 2010 12:34 AM To: [email protected] Subject: [p2-dev] How to build an update site for a product?, Hello there, During the headless build of a product, an update repository is created. But it only contains the features/plugins. Wonder how to build a site which can ship a new release of the product. For instance, a 3.6.1 product which can be installed as update to 3.6.0. Thanks. Best Regards Samuel Wu_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
