Remove Map null annotation workarounds (#8916)
These workarounds to prevent false positives can be removed now the EEAs allow for proper null analysis. Signed-off-by: Wouter Born <github@maindrain.net>
This commit is contained in:
@@ -79,14 +79,14 @@ public class NetworkDiscoveryService extends AbstractDiscoveryService implements
|
||||
|
||||
@Override
|
||||
@Activate
|
||||
public void activate(@Nullable Map<String, @Nullable Object> config) {
|
||||
public void activate(@Nullable Map<String, Object> config) {
|
||||
super.activate(config);
|
||||
modified(config);
|
||||
}
|
||||
|
||||
@Override
|
||||
@Modified
|
||||
protected void modified(@Nullable Map<String, @Nullable Object> config) {
|
||||
protected void modified(@Nullable Map<String, Object> config) {
|
||||
super.modified(config);
|
||||
// We update instead of replace the configuration object, so that if the user updates the
|
||||
// configuration, the values are automatically available in all handlers. Because they all
|
||||
|
||||
Reference in New Issue
Block a user