Hi Samuel, to be honest - i never tried updating the base product itself but i have to try. i think that it should work if i simply export the product onto the repository. because of the fact that p2 only updates the IUs required to update, i think it's no problem as long as i do not update the system bundle - i have to check this also :-)
greetings, michael Am 09.09.2010 um 14:39 schrieb Samuel Wu: > Thank you for the suggestion, Michael. I understand that the features > included in a product can't be updated without updating the product itself > and I've set up something similar to yours to work around this issue. Just as > in your case, what are you going to do if you find you need to ship a new > osgi runtime or webserver? Although the product package works as a stub and > its size is small, it still has the chance to be updated. My question is how > you are going to ship that update to the product. It's more important in your > case because your customer has to pick up the product as a stub and reinstall > the real features after the product update. > > Best Regards > > Samuel Wu > > > <graycol.gif>Michael Mangeng ---09/09/2010 07:43:48 AM---Samuel, P2 searches > the update site for bigger versions of the IUs installed local. > > <ecblank.gif> > From: <ecblank.gif> > Michael Mangeng <[email protected]> > <ecblank.gif> > To: <ecblank.gif> > P2 developer discussions <[email protected]> > <ecblank.gif> > Date: <ecblank.gif> > 09/09/2010 07:43 AM > <ecblank.gif> > Subject: <ecblank.gif> > Re: [p2-dev] How to build an update site for a product? > <ecblank.gif> > Sent by: <ecblank.gif> > [email protected] > > > > Samuel, > > P2 searches the update site for bigger versions of the IUs installed local. > Then it presents the result to you. What matters matters are the "root > components" (don't know how the p2 guys call those) like your product. > > e.g.: the whole software is installed by deploying 1 product - this product > contains 10 sub-features or plugins => you can only update this product e.g. > 3.6.0 to 3.6.1 - but you cannot update one of the sub-features because the > product stats that it needs the exact versions of plugin/feature x defined in > the product. > > with this approach you get 1 big build, which is only updateable as a whole. > > for my case (building automation server) i created a "base > installation"-product. > in my case this contains: > + osgi runtime > + webserver > + a plugin which exposes a p2 administration servlet - there i can manage > repositories, perfom updates, install new features and do reverts. (i want to > set this open source but in the last days i can't find time to create some > docs for it...) > > => then i export this product and deploy it where it has to run. > > after this i can open the p2 admin website of this installation in the > browser and install what is needed for this specific installation. > > the advantages are: > + you got a minimized installation > + you can update sub-components also => you don't need to build "a big new > product" for every bugfix. > > if i want to update a feature, i simply increment the version of the changed > plugins and the version of the feature. then export it on the update site and > it can be installed. > > hope this helps for your case. > > greetings, > Michael > > Am 08.09.2010 um 19:55 schrieb Samuel Wu: > 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 > > > <graycol.gif>"Yousouf, Shenol" ---09/08/2010 03:19:26 AM---Hello Samuel, I am > sorry if I do not grasp some of the details in your use case so you may > already b > <ecblank.gif> > From: <ecblank.gif> > "Yousouf, Shenol" <[email protected]> > <ecblank.gif> > To: <ecblank.gif> > P2 developer discussions <[email protected]> > <ecblank.gif> > Date: <ecblank.gif> > 09/08/2010 03:19 AM > <ecblank.gif> > Subject: <ecblank.gif> > Re: [p2-dev] How to build an update site for a product? > <ecblank.gif> > Sent by: <ecblank.gif> > [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 > > > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
