Hi Bertrand, Thank you for your quick answer. 2015-03-19 19:00 GMT+03:00 Bertrand Delacretaz <[email protected]>:
> Ok, so your problem is that many pom.xml files from the Sling modules > have duplicated <dependency> entries, right? > Yes, that's exactly what I mean. > If that's what you mean that's by design - the high modularity of > Sling and the OSGi dependency rules make it much better for each > module to have its own list of dependencies. We do have some common > dependencies in the Sling parent pom but only very few, by design. > > Always depending on the latest version of an API, like you would do in > more static systems, would be counterproductive as a module might not > actually need that latest version. So it's good for the Sling modules > to have their own lists. > > Does this clarify it for you? Yes, thank you. I didn't know that. Thank you for the clarification. Best, -Petr
