Re: [p2-dev] RCP check-for-update standard behavior

[Ed Merks <ed.merks@xxxxxxxxx>]

Julien,

Generally only the root installed features will be checked for updates.  But depending on how these features' recursive requirements are exactly specified, that may or may not allow for updates of those indirect requirements (on various other features and bundles).   But generally the p2 metadata produced for a feature.xml will lock in very specific versions of their included bundles and features which prevents those from being updated to a different version.  That's sometimes annoying and then folks will use p2.inf information to specify looser requirements.  E.g., the platform uses EMF but in an installation of some Eclipse package/product the users want to be able to update/install a newer version of EMF.

Regards,
Ed

On 21.03.2019 11:22, Julien DEHAUDT wrote:

Hi all,

 

I’m working on an Eclipse RCP with update process enabled; check for update works like a charm, relying on our product repository (internal company server).

 

Today we are asked to integrate the Marketplace feature. This is also already working fine thenceforth we declare an Eclipse repository URL from the Available Software Sites list. Otherwise there are often some unresolved features errors during Marketplace features install.

But this point generates questions on the check for update mechanism, do having Eclipse repository declared could propagate Eclipse updates “behind our back” at each startup?

When we had only our repo url it was ensuring to propagate only our updates, but now that 2 urls are defined.. what could happen.

 

My understanding of Eclipse/RCP is that only features defined in .product, those available in “Installed Software” tab, are in the scope of this check for update feature, but having some more opinions from p2-experts could help me to feel for comfortable with.

 

Thanks by advance

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/p2-dev