Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon

Thanks Mickael, good suggestion to use the downported plug-in as reference. Am 25.02.2016 8:58 vorm. schrieb "Mickael Istria" : > On 02/25/2016 07:50 AM, Lars Vogel wrote: > > Thanks for the clarification Mickael and Tom. FYI, there is no real > dependency, it is a downport of

Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon

Thanks for the clarification Mickael and Tom. FYI, there is no real dependency, it is a downport of some Neon feature to Mars, which I want to enable only for Mars. Am 24.02.2016 3:07 nachm. schrieb "Thomas Watson" : > Mickael is correct. There is no capability defined which

Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon

Mickael is correct. There is no capability defined which indicates the eclipse release name. The version dependencies are what should be used. Tom From: Mickael Istria To: equinox-dev@eclipse.org Date: 02/24/2016 03:26 AM Subject:Re: [equinox-dev]

[equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon

Hi, 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. Best regards, Lars