This in itself seems to fix issues of OskariComponents initializing in an order that causes errors when the code is compiled with Java 11. The problem was not at compile time but at runtime/startup. It also allows us to define the order in which the components are initialized if we need to. Like MapLayerService component might need to be initialized before some component that uses the service.

Usage (when needed, order defaults to max int and looks like everything works currently on Java 11):

@Oskari(order = 1000)
@OskariActionRoute(value="LayerAdmin", order=1500)