Scope change is only necessary for feature generator thus we should avoid that to not promote new dependencies to jackson users. This might cause a push back later on as somebody will need to manage dependency brought by new jackson release which he hasn't had before. I believe we can still explicitly define these in feature fragment using <bundle> part and leave maven part.
Cheers, Łukasz pon., 27 sty 2020 o 17:17 Steinar Bang <s...@dod.no> napisał(a): > >>>>> Łukasz Dywicki <l...@code-house.org>: > > > Hey, as changes were made last year I would not hold it too long. As > > long as integration doesn't break Jackson build we should be fine. In > > worst case we will have to raise an issue in jackson issue > > tracker. ;-) > > The changes that I'm most unsure about, are the dependency scope changes > (I've changed all of the dependencies that are pulled in by features to > have <scope>provided</scope> and that in turn meant that I've had to add > dependencies that were previously pulled in as transitive dependencies, > just to make maven build). > >
