Community
Participate
Working Groups
Build ID: M20090204-1400 Steps To Reproduce: Previously, the validation framework did not provide an easy way to get and manipulate the state of validators. The only way to do this was to use internal classes that could potentially (and did) change between releases. The introduction of the ValidationFramework class as a Provisional API is a step in the right direction. However, some of the previous problems with using internal classes remain as the ValidationFramework and associated classes expose internal classes: - MutableWorkspaceSettings exposes GlobalPreferencesValues - ValidationResult exposes ValidationException, IReporter - ValidationFramework exposes DependencyIndex, ProjectUnavailableError, IReporter - Validator.V1 exposes ValidatorMetaData - Validator exposes FilterGroup, IValidator (this does not inlcude instances of public methods of Validator that take internal classes as arguments) According to http://wiki.eclipse.org/WTP_API_Policy, Provsional API will not change on a release or maintenance release and internal API can be changed at anytime. However, it seems to me that a Provisional API that returns internal classes is not really Provisional API, because the API can be broken if an exposed internal class is changed/moved/removed. More information:
