The individual artifacts are fine and they where already part of parent pom 32 for the annotations. Not having the annotations in the parent pom requires to repeat this in each and every project now, making the move from anything below 33 to 33 a pain.
Regards Carsten Konrad Windszus wrote > Actually Oli switched to individual spec chapter artifacts and there was also > some discussion triggered by me in the comments (e.g. > https://issues.apache.org/jira/browse/SLING-7384?focusedCommentId=16327408&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16327408). > > It was you Carsten, who answered and said > "But again, in general its better to use the above mentioned single purpose > artifacts". > > Therefore you have to include the individual annotation artifacts (which are > all managed in parent) in your project! > Please clarify if there was some misunderstanding there. > Konrad > >> On 26. Feb 2018, at 12:15, Carsten Ziegeler <[email protected]> wrote: >> >> Hi >> >> it seems that updating to parent pom 33 is way harder than it should be. >> For an unknown reason the OSGi annotations are no longer declared as >> dependencies, requiring now each and every project to define >> them...which I think is really annoying. >> >> The change in question is referencing SLING-7384, but I can't find a >> discussion nor reason in there. So why has this been done? >> >> Regards >> Carsten >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> [email protected] > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
