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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: Lars Vogel <lars.vogel@xxxxxxxxxxx>
Date: Wed, 24 Feb 2016 10:22:58 +0100
Delivered-to: equinox-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/equinox-dev>
List-help: <mailto:equinox-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/equinox-dev>, <mailto:equinox-dev-request@eclipse.org?subject=unsubscribe>

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

Follow-Ups:
- Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon
  - From: Mickael Istria

Prev by Date: Re: [equinox-dev] Provide capability question
Next by Date: Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon
Previous by thread: [equinox-dev] Provide capability question
Next by thread: Re: [equinox-dev] Ensure that a plug-in is valid for Mars but not for Neon
Index(es):
- Date
- Thread

Back to the top