Hi Am 25.01.2012 um 03:59 schrieb Justin Edelson:
> also reverted r1235541 in r1235608. I think this is correct. If not, I > apologize. Nothing to apoligize for -- it was me starting this mess out of a problem updating to 2.3.7; so I would have to apologize. Thanks for reverting anyway. Where does this come from: We have the DavEx bundle which embeds the Jackrabbit JCR Server library which depends on stuff from the Jackrabbit SPI library/bundle. All fine so far. Now, Jackrabbit SPI introduced a backwards-compatibility breaking change from 2.3.6 to 2.3.7 and now exports the API correctly at version 3.0 (was 2.4.0 before). This now puts the DavEx library in a problematic situation with embedding the JCR Server library: * When embedding 2.3.7, other Jackrabbit bundles must also be 2.3.7 * When embedding 2.3.6, other Jackrabbit bundles must also be 2.3.6 Our problem with this is, that our DavEx bundle has problematic indirect version dependency due to this embedding. We should probably not embedd at all but Jackrabbit JCR Server should export the package(s) required by us. I have been proposing that to Jackrabbit community. Regards Felix > > On Tue, Jan 24, 2012 at 9:48 PM, Justin Edelson > <[email protected]> wrote: >> reverted in r1235605 >> >> On Tue, Jan 24, 2012 at 7:01 PM, Felix Meschberger <[email protected]> >> wrote: >>> The Sling build currently fails due Jackrabbit SPI 2.3.7 intriducing a >>> backwards compat break. >>> Wanted to go back to 2.3.6 in Davex and builder but my PC just went to >>> sleep lacking power.... >>> Will fix this tomorrow >>> Regards >>> Felix
