|Re: [p2-dev] RCP check-for-update standard behavior|
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.
Back to the top