| Re: [p2-dev] IRequiredCapability internal? |
IRequiredCapability was limiting in what it could express. For example it could not express negation and or'ing, and it could only described dependencies on something that had a namespace, a name and a version and we are striving to express requirements and capabilities on other things (for example BundleExecutionEnvironment). As such, to ensure for API evolution we have turned the too specific IRequiredCapability into an IRequirement.
IProvidedCapability is still API, but it is very likely that it will either be turned into something more generic, or be marked internal if we don't have the time to make it API.
As for IRequirementChange the reference to IRequiredCapability is something that we have still left to do (https://bugs.eclipse.org/bugs/show_bug.cgi?id=299506)
The situation of the API now is that we have tried to move all the types that we needed to see made API in a final package for M5, however we still have work to do to reach the final state for 3.6 (hopefully by M6).
If you have feedback, it is very much appreciated,
HTH
Thomas M Houser ---22/01/2010 03:23:08 PM---I'm migrating from Eclipse 3.5 to Eclipse 3.6 (I20100119-0800). Can someone explain why IRequiredCapability is now internal in
From: | Thomas M Houser <tmhouser@xxxxxxxxxx> |
To: | p2-dev@xxxxxxxxxxx |
Date: | 22/01/2010 03:23 PM |
Subject: | [p2-dev] IRequiredCapability internal? |
