On Wed, 2018-05-30 at 11:26 +0200, Julian Reschke wrote: > On 2018-05-30 09:31, Robert Munteanu wrote: > > Hi, > > > > On Sun, 2018-05-27 at 09:10 +0200, Julian Reschke wrote: > > > FWIW, > > > <https://github.com/apache/sling-org-apache-sling-jcr-contentload > > > er/b > > > lob/master/pom.xml> > > > shows a few ancient (or even end-of-lifed) Jackrabbit > > > dependencies. > > > > > > I would recommend to update to the latest stable release > > > applicable > > > for > > > the Java version you need to support > > > (<http://jackrabbit.apache.org/jcr/jackrabbit-roadmap.html>). > > > > I am not sure that this is cause of concern for this particular > > release. We only use those dependencies at compile-time so that bnd > > can > > calculate the proper import ranges. > > ... > > And at test time, right? I would argue that you should not test with > an > end-of-lifed version of a library.
The ITs are configured separaretly, see [1], and that should change to use a supported version. The unit tests OTOH I think are fine to run even on unsupported release. Robert [1]: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/test/java/org/apache/sling/jcr/contentloader/it/PaxExamUtilities.java#L49-L50
