[riena-dev] Making Nop API ?

[Elias Volanakis <elias@xxxxxxxxxxxxxxxxx>]

Any objections against making the class Nop API  (i.e. not internal) ?

Background: Nop is internal but is used in about of our 10 plugins.
This results in about 80 warnings of the form "Discouraged access: The
type Nop is not accessible...". I would like to get rid of these
warnings because they make the "real" warnings harder to find. Nop
does not do much (hence the name) so I don't see a problem with making
it API.

Let me know if you have objections...

Kind regards,
Elias.

-- 
Elias Volanakis | Technical Lead | EclipseSource Portland
elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | http://eclipsesource.com