On 02/24/2016 10:22 AM, Lars Vogel
A plugin doesn't really care if it's Neon or Mars, what matters is
more the version of its dependencies. Instead of checking the
version of core.runtime, it seems better to identify the bundle or
package that makes the compatibility and to put the restriction on
this one directly.
What is the recommended way to define that a
plug-in is valid only for Eclipse Mars but not for Eclipse Neon?
I currently use a versionized manifest dependency to
core.runtime with a max value but I'm not sure if that is the