Although not wrong the current way to use @SuppressWarnings("nls") on
method level instead of using //$NON-NLS-1$ on string constants causes
warnings in the log:
At least one of the problems in category 'nls' is not analysed due to a
compiler option being ignored
Maybe it is an option to switch to using "$NON-NLS-1$" to reduce
warnings to make it easier not to overlook an important warning.

Change-Id: I965403a43369cb4e164f9295ca1941d1a9f9d0f5
Signed-off-by: Carsten Hammer <carsten.hammer@t-online.de>