I have no problem. There was an ask to update to a newer API. Which Robert pointed out that didn't need to be done. But he did suggest updating the JCR API that was being used by the Pax Exam.
Which is where I encountered, what I consider an odd problem, that when I update the version of the JCR API in the Pax Exam configuration it creates all sorts of problems in the build. I never use Pax Exam, so I'm probably just missed a step or something, but at this point I have no great desire to learn it. So I'll leave that to someone who has a better understanding. - Jason On Mon, Jun 11, 2018, at 3:21 PM, Oliver Lietz wrote: > On Monday 11 June 2018 09:23:08 Jason E Bailey wrote: > > So I've ran into a wall on this. There seems to be a synchronicity between > > the JCR api which is used as the basis for the build and the JCR api used > > by PAX exam. I can't touch one without touching the other and everything > > fails. > > Both bundles provide JCR API 2.0 – what's your problem? > > > Right now I'm looking at > > > > 1. Restarting the VOTE with the code as is and working, and no updates to > > the JCR API 2. Creating a story for updating the PAX Exam in this. > > Why do you think updating Pax Exam will solve your problem? > > I suggest getting rid of that ugly boilerplate code, cleaning up tests and > using Testing PaxExam. > > Regards, > O. > > > If I don't hear otherwise in the next couple of days I'll kick the vote off. > > > > > > - Jason > > > > On Wed, May 30, 2018, at 7:40 AM, Robert Munteanu wrote: > > > 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/ma > > > ster/src/test/java/org/apache/sling/jcr/contentloader/it/PaxExamUtilities. > > > java#L49-L50 >
