>>>>> Łukasz Dywicki <l...@code-house.org>: > 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.
Yes, this was my worry. (on the other hand, some of these dependencies were already <scope>provided</scope>, so FWIW it's more consistent in my change branch...) > I believe we can still explicitly define these in feature fragment using > <bundle> part and leave maven part. I don't understand what you mean here.
