|Serving Eclipse version-specific features from a single p2 update site? [message #133361]
||Thu, 18 June 2009 14:08
| Jason Parekh
Registered: July 2009
We have different compiled bits of our Eclipse plugin for each version of
Eclipse (we used internal APIs that changed across versions). Is there a
clean way of giving users a single update site URL which would only show
features applicable to the user's version of Eclipse?
I read somewhere that P2 hits content/artifacts first, and in its absence
falls back on site.xml. Given this, it seems we can achieve this single
URL to separate 3.3 from 3.4+3.5. However, users of 3.4 and 3.5 would see
both versions of our features. Is there any metadata I could stick on the
IU to have the non-applicable features be omitted from P2 UI?
Powered by FUDForum
. Page generated in 0.01534 seconds