Re: AW: [riena-dev] Making Nop API ?

[Stefan Liebig <Stefan.Liebig@xxxxxxxxxxxx>]

Done:
- "moved" to org.eclipse.riena.core.util
- updated all riena sources referencing Nop
- @deprecated internal version

Tschüß,
Stefan

Schenkel, Thorsten wrote:
> +1
>
> greetings
>
> Thorsten
>
> -----Ursprüngliche Nachricht-----
> Von: riena-dev-bounces@xxxxxxxxxxx [mailto:riena-dev-bounces@xxxxxxxxxxx] Im Auftrag von Elias Volanakis
> Gesendet: Mittwoch, 5. August 2009 21:32
> An: Riena Developers list
> Betreff: [riena-dev] Making Nop API ?
>
> 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.
>
>