[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] What can enablement filters contain?
- From: Terry Parker <tparker@xxxxxxxxxx>
- Date: Thu, 18 Jun 2009 10:30:43 -0700
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:date:message-id:subject:from:to:content-type:x-system-of-record; b=r5T3lAlhdTYnIpilYi5l4Faa/PHr18+yHAa2geluwobeGFPRDo8NYqtxWL+yKwYAt uS3NbsC7ozAH+CNegAS/w==
I've never seen anything more than ws/os/arch and the "org.eclipse.update.install.features=true" profile property in an enablement filter. Can other properties be used?
Specifically, can I hide an IU that is only known to work with Eclipse 3.4 via this mechanism? I'm wondering if I can provide different versions of a feature in the same repository and have the Eclipse UI only present the version that matches their base install.