Konrad Windszus wrote > 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?
I don't know the exact reason, but while this could be considered a regression, I don't think we should regard it as one. The solution is simple: don't blindly update to parent pom 30. There is no need atm to do so. It's good to have a parent pom which shows latest best practice and doesn't use the obsolete stuff anymore. If you move to the R6 annotations, move to version 30. In the last weeks I've already converted several projects, others have done similar. So it's only a matter of time until we have migrated all projects. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
