On 02/24/2016 10:22 AM, Lars Vogel wrote:
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 best approach.
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.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
equinox-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev
