Force settings of protect.yaml

The settings defined in the protection entries of the protect.yaml protection definition can also be specified directly in programming languages that support annotations see WUPI->Annotations.

If conflicts occur, the annotation is preferred by default, since the reference to the code has more weight here. However, if you want to force the entry in the protect.yaml protection definition, this is possible with the override parameter.

For example, the following definition causes foo to be assigned to license list 45 in any case, regardless of which annotation this function has.

Protection:

- Type: function

   Name: foo

   LicenseListId: 45

   Override: True