[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] What can enablement filters contain?


You can filter on any property defined in the profile. There is no specific property denoting an Eclipse 3.4 versus 3.5 install, but you could always add a new property for 3.5-based installs and then filter on the existence of that new property.

John



Terry Parker <tparker@xxxxxxxxxx>
Sent by: p2-dev-bounces@xxxxxxxxxxx

06/18/2009 01:30 PM

Please respond to
P2 developer discussions <p2-dev@xxxxxxxxxxx>

To
P2 developer discussions <p2-dev@xxxxxxxxxxx>
cc
Subject
[p2-dev] What can enablement filters contain?





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.

Thanks,
Terry Parker
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev