Community
Participate
Working Groups
Make it an error to reference API with newer @since tag than the import range in the MANIFEST. For example, if an api has @since 3.7, but the use of that api is in a bundle has this in the MANIFEST: Require-Bundle: org.eclipse.cdt.core;bundle-version="[3.6.0,4.0.0)" then there should be an API error because p2/osgi can select a version of the dependency that does not work.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.