|Re: [p2-dev] Bundle not unpacked after update|
You can try debugging UnzipAction#execute located in org.eclipse.equinox.p2.touchpoint.natives bundle.
Also, you can check the status of your operation for more details. If you’re using p2 director for the update, check the result of DirectorApplication#run (org.eclipse.equinox.p2.director.app). It’s a multistatus containing details of the executed sub-steps along the update - if you look at the object with a debugger you may find something useful.
I don't have a small example of this behaviour, but it seems to be an issue with access privileges.
I've found out that if I install RCP product in a location different than C:\Program Files ... update works just fine.
Does p2 report any issues with access privilleges when unzipping bundles?
I've also noticed that this problem occurs only for some of the bundles marked for unzipping. Others are unpacked properly in the same loaction during update.
I can try to debug this scenario, if you can point me to the places in the code where unpacking happens.
I'm using p2 bundles form Indigo update site.
2012/1/4 Bourgeois, Christian <Christian.Bourgeois@xxxxxxxxxxxxx>
We came across the same issue some time ago and we found a way to make this uses case working.
In the bundle you want to be unzipped at installation time, just add the following line to the META-INF/MANIFEST.MF file:
It worked like a charm for us with 3.6 and 3.7.
Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
I have a feature that contains plugin which is marked to be unpacked after installation. However after updating this feature to a newer version this plugin remains as a jar. Both generated profile and update site metadata look correct, plugin's unit definition contains
anyway, the new plugin is downloaded but not extracted.
Just for test I removed instruction key='zipped' from update site metadata and it fixed the issue...
Any hints will be appreciated!
Back to the top