Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Require bundle has upper version requirement of 4.0, 0?

Hi Leo,

A really good reference on this is: https://wiki.eclipse.org/Version_Numbering#How_to_specify_plug-in_requirements

HTH
Jonah


On 30 Sep 2016 9:52 p.m., "Dirk Fauth" <dirk.fauth@xxxxxxxxx> wrote:

Hi,

The upper bound is not related to compiling. It is related to the runtime resolution to ensure that you only bind to a bundle version that is API compatible.

We also ensure this at the bundle installation time by using features. But taking semantic versioning seriously, the upper bound should be specified.

Hope that helps,
Dirk


Am 30.09.2016 22:09 schrieb "Leo Ufimtsev" <lufimtse@xxxxxxxxxx>:
Hello,

I often see something like:

Require-Bundle:
...
 org.eclipse.ui.views;bundle-version="[3.3.100,4.0.0)",

I.e, upper bound of 4.0.0.

Is the idea here so that if there is API breakage in dependent plugin, the plugin will stop compiling, or is there other reasoning for this?

Thank you.

---
Leo Ufimtsev | Software Engineer @ Red Hat
Email: Leonidas@xxxxxxxxxx
IRC:  freenode # swt 
Twitter: @LeoUfimtsev

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

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

Back to the top