Re: [p2-dev] Update mechanism
Hi Dave, thanks for the tutorial. I set up the example rcp application as described in lab-2 of the tutorial in osgi-arch-patterns. These are the steps I did: 1. Edit the Application.java class with the installFeature-Code 2. Added an UpdateHandler calling an UpdateOperation by executing a menu entry in the running application 3. Export the product as described 4. Created the perspective plugin/feature/updatesite 5. Started the exported product and the view of the created perspective plugin will be shown 6. I changed a visible entry in the view, the version of the plugin and feature 7. Updated the site.xml and created the p2 update site 8. Started the exported product containing the installed feature (version 1.0.0) and excuted the menu entry UpdateOperation I inserted some output during update. This is the result: !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.391 !MESSAGE Execute UpdateHandler! !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.399 !MESSAGE Execute updateFeature! !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.482 !MESSAGE Checking update site for updates: http://localhost:8085/labs/lab-2/com.example.app.perspectives.p2/ !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.953 !MESSAGE Units to update: 4 !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.960 !MESSAGE Unit to update: com.example.app.perspectives.feature.feature.group Version: 1.1.0.201603311551 !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.967 !MESSAGE Unit to update: com.example.app.perspectives.feature.feature.jar Version: 1.1.0.201603311551 !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.974 !MESSAGE Unit to update: Default Version: 1.0.0.21-cKxK367735E39955CC5 !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:01.981 !MESSAGE Unit to update: com.example.app.perspectives Version: 1.1.0.201603311551 !ENTRY org.eclipse.equinox.p2.operations 1 1 2016-03-31 15:52:02.242 !MESSAGE No updates were found. !ENTRY com.example.app.perspectives 1 0 2016-03-31 15:52:02.249 !MESSAGE Update finished! The IMetadataRepository recognizes the features in new versions but the status of the UpdateOperation#resolveModal() is „No udpates were found.“. Can you give me a hint what may be wrong here? Best regards, Alex Von: p2-dev-boun...@eclipse.org [mailto:p2-dev-boun...@eclipse.org] Im Auftrag von David Orme Gesendet: Mittwoch, 30. März 2016 11:21 An: P2 developer discussions <p2-dev@eclipse.org> Betreff: Re: [p2-dev] Update mechanism A bit dated but the general approach still works: https://github.com/coconutpalm/osgi-arch-patterns From an EclipseCon tutorial Patrick Paulin and I gave... Dave Orme On Mar 30, 2016 2:21 AM, "Alexander Gerbig" <ager...@systhemis.de<mailto:ager...@systhemis.de>> wrote: Hi p2-dev team, we are developing a rcp product with a lot of features. The features are included in the product. The update mechanism is developed as described in the tutorial from Lars Vogel (http://www.vogella.com/tutorials/EclipseP2Update/article.html). When I change a plugin/feature and according to that the versions of these and the product the update mechanism works. My question now: Is it possible to just deploy the changed feature into a p2 repository so the update mechanism downloads only this feature? A local test of this scenario was not successful. The rcp application knows the url of the p2 repository where the feature is hosted. When I point the "install new feature" dialog of my IDE on this url the feature will be shown so the repository should be ok. When I deploy the whole rcp product with changed version number as p2 repository the update mechanism works. But in that case the whole product will be downloaded. Is it possible that updating a single feature which is delivered with the product does not work? Thanks for your help! Bye Alex -- Alexander Gerbig, Dipl.-Wirt.-Inf. (FH) Softwareentwicklung und -beratung T +49 931 260 798 13<tel:%2B49%20931%20260%20798%2013> | F +49 931 260 798 29<tel:%2B49%20931%20260%20798%2029> ager...@systhemis.de<mailto:ager...@systhemis.de> | www.systhemis.de<http://www.systhemis.de/> SYSTHEMIS AG | Ein Unternehmen der Prof. Thome Gruppe Mergentheimer Str. 76a | 97082 Würzburg | Zentrale: +49 931 260 798 0 Vorstand: Dr. Christian Schneider Aufsichtsratsvorsitzender: Prof. Dr. Rainer Thome | HRB: 10523 (Würzburg) ___ p2-dev mailing list p2-dev@eclipse.org<mailto:p2-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/p2-dev SYSTHEMIS AG | Ein Unternehmen der Prof. Thome Gruppe Mergentheimer Str. 76a | 97082 Würzburg | Zentrale: +49 931 260 798 0 Vorstand: Dr. Christian Schn
Re: [p2-dev] Update mechanism
What are root level features? I do not see something in the tutorial about that. -Ursprüngliche Nachricht- Von: p2-dev-boun...@eclipse.org [mailto:p2-dev-boun...@eclipse.org] Im Auftrag von Lars Vogel Gesendet: Donnerstag, 31. März 2016 12:10 An: P2 developer discussions <p2-dev@eclipse.org> Betreff: Re: [p2-dev] Update mechanism Hi Alexander, did you try using root level features? This is also described in the tutorial. Best regards, Lars On Wed, Mar 30, 2016 at 9:21 AM, Alexander Gerbig <ager...@systhemis.de> wrote: > Hi p2-dev team, > > > > we are developing a rcp product with a lot of features. The features > are included in the product. The update mechanism is developed as > described > > in the tutorial from Lars Vogel > (http://www.vogella.com/tutorials/EclipseP2Update/article.html). > > > > When I change a plugin/feature and according to that the versions of > these and the product the update mechanism works. My question now: Is > it > > possible to just deploy the changed feature into a p2 repository so > the update mechanism downloads only this feature? A local test of this > scenario was not successful. > > > > The rcp application knows the url of the p2 repository where the > feature is hosted. When I point the "install new feature" dialog of my > IDE > > on this url the feature will be shown so the repository should be ok. > > > > When I deploy the whole rcp product with changed version number as p2 > repository the update mechanism works. But in that case the whole > product will be downloaded. > > > > Is it possible that updating a single feature which is delivered with > the product does not work? > > > > Thanks for your help! > > > > Bye Alex > > > > > > -- > > Alexander Gerbig, Dipl.-Wirt.-Inf. (FH) > > Softwareentwicklung und -beratung > > T +49 931 260 798 13 | F +49 931 260 798 29 > > ager...@systhemis.de | www.systhemis.de > > > > > SYSTHEMIS AG | Ein Unternehmen der Prof. Thome Gruppe Mergentheimer > Str. 76a | 97082 Würzburg | Zentrale: +49 931 260 798 0 > Vorstand: Dr. Christian Schneider > Aufsichtsratsvorsitzender: Prof. Dr. Rainer Thome | HRB: 10523 > (Würzburg) > > ___ > p2-dev mailing list > p2-dev@eclipse.org > To change your delivery options, retrieve your password, or > unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/p2-dev -- Eclipse Platform UI and e4 project co-lead CEO vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: http://www.vogella.com ___ p2-dev mailing list p2-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/p2-dev SYSTHEMIS AG | Ein Unternehmen der Prof. Thome Gruppe Mergentheimer Str. 76a | 97082 Würzburg | Zentrale: +49 931 260 798 0 Vorstand: Dr. Christian Schneider Aufsichtsratsvorsitzender: Prof. Dr. Rainer Thome | HRB: 10523 (Würzburg) ___ p2-dev mailing list p2-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/p2-dev
