|
| Re: API for validators [message #227544 is a reply to message #227537] |
Thu, 05 February 2009 15:30   |
Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
I recommend Openning a bug request for internal API to be made as Public
API where needed.
One thing in WTP we do not do is make enough items public API. In fact
we technically should not be calling each others internal API between
plugins. If we need functionality between our plugins, we should have
public API. Internals should remain internal to the plugin.
It's one of the reasons that the release train has a requirement for
plugins on that train not to use internal API from other plugins.
Dave
Nadeem wrote:
> It appears there is no public API for manipulating the state of
> validators on a project. For example, disabling the build/manual
> setting or adding/removing filters.
>
> Using the changing internal API's is not a good option, because it means
> being tied to specific versions of WTP where that internal API has not
> changed.
>
> Another option is to use the Eclipse preferences to manipulate the
> validation preferences directly. This is a better option, because the
> persisted values in the preferences would need to maintain the same
> structure between WTP releases.
>
> Both options, using the internal API or the preferences directly, aren't
> good options, but the preference option seems to be "less" bad. Does
> anybody have any other ideas/suggestions?
>
> Thanks,
> Nadeem
>
|
|
|
| Re: API for validators [message #227545 is a reply to message #227544] |
Thu, 05 February 2009 18:05 |
 Nadeem Aboobaker
Messages: 20
Registered: July 2009 |
Junior Member |
|
|
Thanks for the reply.
The good news is that I've found a provisional API that provides some of
the functionality I need (org.eclipse.wst.validation.ValidationFramework).
I'm still trying it out to see if it provides what's needed or not.
After my testing and seeing what works and doesn't, I'll definitely open a
bug request as you mentioned.
- Nadeem
David Carver wrote:
> I recommend Openning a bug request for internal API to be made as Public
> API where needed.
> One thing in WTP we do not do is make enough items public API. In fact
> we technically should not be calling each others internal API between
> plugins. If we need functionality between our plugins, we should have
> public API. Internals should remain internal to the plugin.
> It's one of the reasons that the release train has a requirement for
> plugins on that train not to use internal API from other plugins.
> Dave
> Nadeem wrote:
>> It appears there is no public API for manipulating the state of
>> validators on a project. For example, disabling the build/manual
>> setting or adding/removing filters.
>>
>> Using the changing internal API's is not a good option, because it means
>> being tied to specific versions of WTP where that internal API has not
>> changed.
>>
>> Another option is to use the Eclipse preferences to manipulate the
>> validation preferences directly. This is a better option, because the
>> persisted values in the preferences would need to maintain the same
>> structure between WTP releases.
>>
>> Both options, using the internal API or the preferences directly, aren't
>> good options, but the preference option seems to be "less" bad. Does
>> anybody have any other ideas/suggestions?
>>
>> Thanks,
>> Nadeem
>>
|
|
|
Powered by
FUDForum. Page generated in 0.03929 seconds
] 
Search
Help
Register
Login
Home
