Konrad Windszus wrote > >> On 29 Mar 2017, at 10:29, Oliver Lietz <[email protected]> wrote: >> >> On Wednesday 29 March 2017 08:44:59 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 guess it's one of SLING-6246, SLING-6532 or SLING-6533. > > The latter two should lead to failures at compile time already (if e.g. the > SCR annotations can no longer be resolved). > If it is SLING-6246 that sounds like a major regression in the > maven-scr-plugin itself then, which is probably worth investigating.
The problem is that many poms have the scr annotations as an explicit dependency. So when updating to parent 30 you still have that dependency and don't get compilation problems Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
