It seems that parent 30 breaks the usage of the maven-scr-plugin. With 29 it
works. When looking at the history of the parent pom.xml
(https://github.com/apache/sling/commits/trunk/parent/pom.xml) I don't really
see the reason for that.
If I understand correctly reverting to parent 29 makes everything work as
before. Although I do agree that we should migrate all modules in the future
towards OSGi annotations and get rid of the maven-scr-plugin, having a broken
maven-scr-plugin integration in parent 30 feels like a regression to me. Does
anyone have a clue what the issue is with parent 30 here?
Thanks,
Konrad
