On Mar 31, 2011, at 5:43 PM, Craig Ganoe <[email protected]> wrote:
> As I said in one of my longer emails, the only Sling code change I noticed is > that Sling's PluggableDefaultAccessManager makes a call to canRead(itemPath) > on its superclass in Jackrabbit - DefaultAccessManager. For some reason > unclear to me they changed it in from just taking a path as a parameter in > 2.1 to taking both a path and an item ID in 2.2, but then the JavaDocs say > either one of the parameters can be null. This was discussed both on sling-dev and jackrabbit-dev. IIRC, it was actually done in 2.1.3. I posted a potential patch on sling-dev when this initially came up. Justin > > I made a little progress today, but unfortunately, due to the absurdities of > today's build tools, I'm stuck with a bunch of vague messages that have > nothing to do with actually building the software. That today you can't > replace a few libraries and a few lines of code and still build software > without causing miles of vague errors that have nothing to do with the > compilability of the actual code is ridiculous. > > [INFO] Scanning for projects... > [WARNING] > [WARNING] Some problems were encountered while building the effective model > for > org.apache.sling:org.apache.sling.testing.samples.integrationtests:jar:0.1.1-SNAPSHOT > [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must > be unique: org.apache.sling:org.apache.sling.junit.remote:jar -> duplicate > declaration of version 0.1.1-SNAPSHOT @ line 272, column 21 > [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must > be unique: org.apache.sling:org.apache.sling.testing.tools:jar -> duplicate > declaration of version 0.1.1-SNAPSHOT @ line 277, column 21 > [WARNING] > [WARNING] It is highly recommended to fix these problems because they > threaten the stability of your build. > [WARNING] > [WARNING] For this reason, future Maven versions might no longer support > building such malformed projects. > [WARNING] > > On Mar 31, 2011, at 2:24 PM, Eric Norman wrote: >> Hi All, >> >> I found a use case where I could also use an upgrade to jackrabbit 2.2.5 to >> utilize some changes in user/group management. I filed JIRA >> issue SLING-2044 for tracking and will attempt the upgrade today. >> >> Regards, >> Eric >> >> On Fri, Mar 25, 2011 at 8:23 AM, Justin Edelson >> <[email protected]>wrote: >> >>> On Fri, Mar 25, 2011 at 9:03 AM, Ian Boston <[email protected]> wrote: >>>> >>>> On 25 Mar 2011, at 12:54, Justin Edelson wrote: >>>> >>>>> >>>>> >>>>> On Mar 24, 2011, at 5:06 PM, Ian Boston <[email protected]> wrote: >>>>> >>>>>> >>>>>> On 24 Mar 2011, at 20:44, Craig Ganoe wrote: >>>>>> >>>>>>> >>>>>>> Is there any documentation for upgrading the jackrabbit version in the >>> Sling build? >>>>>> >>>>>> AFAIK, there is not. >>>>>> Ian >>>>> >>>>> There is, in a sense. Look at JIRA and Subversion and you'll see the >>> exact set of changes made for prior upgrades. >>>> >>>> good point, >>>> >>>> >>> https://issues.apache.org/jira/browse/SLING-1660?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel#issue-tabs >>>> >>>> http://svn.apache.org/viewvc?view=revision&revision=987559 >>>> >>>> was that the right issue ? >>> >>> SLING-1531 too... >>> >>>> >>>> Ian >>>> >>>> >>>>> >>>>> Justin >>>>>> >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>>> Craig >>>>>>> >>>>>> >>>> >>>> >>> >
