Defining the theme for a super class of a view does not work

[Artur-]

@Theme(Lumo.class)
public class AbstractView extends Div {

@Route("Upload")
public class UploadView extends AbstractView {

Fails on deployment with

com.vaadin.flow.server.InvalidApplicationConfigurationException: Found configuration annotations that will not be used in the application. 
Move the following annotations to a single route or the top RouterLayout of the application: 
Non RouterLayout: test.AbstractView contains: Theme

[caalador]

Neither AbstractView nor UploadView is a RouterLayout nor do they define @Route.

[Artur-]

Added missing @Route, which is present on the view class

[pleku]

Why is not AbstractView actually abstract ? We could skip the error for abstract class and interface and instead just log on trace level.

The use case for having just one location for the @Theme for all views in the app is very valid. Same kind of goes for the PageConfigurator also. But is it too cumbersome to have a RouterLayout just for that ?

[pleku]

Should also update our flow-component-base to apply @Theme(Lumo.class) after this to make it apply the theme for all of out demos.