Hello Pascal, Thanks for responding. Comments below
Pascal wrote on 06/08/2011 12:00:16 PM: > Hi David, > > Sorry for not answering to you earlier. > Could you please describe in more detail what you mean by "the > bundles that did not get installed by p2"? > How did those get in? What sort of behaviour would you expect? Sure, let me describe a bit more. We have a full osgi app running on equinox. Our build generates what I though was a p2 enabled driver. Driver includes launcher and all application bundles under plugins directory. The build also generates a p2 repository that we export to our test site. This drivers will get layout not using the p2installing but Install Anywhere installer instead. Once the driver gets install people can start running our app, no problems. If they want an update they can point to a p2 repository we give them and then run some simple commands we created around your p2 InstallOperation and UpdateOperations services. My logic is this. I first find the IUs that are completely new bundles not found in DefaultProfile, then I use InstallOperations to install that list. Then I figure out IUs that are new versions of existing IUs and I update those using the UpdateOperations service. Here is what works: I can install new bundles via p2 and I'm able to update those. Here is what I can't get to work: I can't update those bundles that came with the installer, the UpdateOperations claims there is not updates available. I query the DefaultProfile and I see the old version, I query the repo with new metadata and artifacts and I see the new version. No quite sure why update installer is not finding the new updates in the new repo. Another thing I tried was to use your provremove and provinstall commands. That half worked, I'm not able to really uninstall the old version, the two versions run side by side, not what I want. I'm thinking I may need to do something else to make the bundles lay down by installer p2 enabled. What is your take on this issue. > > PaScaL > > On 2011-06-06, at 2:18 PM, David Peraza wrote: > > > Hello, > > > > I sent this note before I subscribed to mailing list, not sure it > went through and sending again. > > > > Regards, > > > > David Peraza > > Software Engineer > > STG Emerging Solutions - Cloud Computing > > https://w3.tap.ibm.com/w3ki2/display/kstart/ES+Technology+Preview+Home > > IBM Rochester, Minnesota > > Phone: (507)253-5383 > > E-mail: [email protected] > > > > "The important thing is to never stop questioning." -- Albert Einstein > > ----- Forwarded by David Peraza/Rochester/IBM on 06/06/2011 02:17 PM ----- > > From: David Peraza/Rochester/IBM > > To: [email protected] > > Date: 06/06/2011 02:00 PM > > Subject: P2 updates and uninstall failled for bundles not > installed using p2. > > > > > > > > Hello, > > > > We are developing an OSGi product and I'm task to code the update > flow. I have selected to go with p2 repositories being the source of > our updates and fixes. Everything is going well I'm able to install > new bundles, updates those bundles I install and even able to > rollback to a specific timestamp. However, when I try to updates > bundles that did not get installed using p2, it fails saying there > is no updates found. I tried un-installing using your provremove > and then install the new version of the bundle using provinstall and > they both succeed. But, when I restart our app I see both version > running side by side, which is something we want to avoid. > > > > Question: > > > > Is there a specific config that I need to preform to our drivers > so that bundles can be updated using p2? > > > > Note: I do see all bundles of the product under the default > profile. So it strikes me as strange that I can't update them. > > > > > > Best Regards, > > > > David Peraza > > Software Engineer > > STG Emerging Solutions - Cloud Computing > > https://w3.tap.ibm.com/w3ki2/display/kstart/ES+Technology+Preview+Home > > IBM Rochester, Minnesota > > Phone: (507)253-5383 > > E-mail: [email protected]
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
