woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest Jackrabbit 2.x URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-483057288 Hi @garydgregory , Yes, the naming is tricky here. The main reason I mentioned is that Jackrabbit2 had upgraded its HttpClient from v3 to v4 since v2.16. [1] Therefore, it is actually okay to use any Jackrabbit 2.x version before 2.16 with the old commons-vfs webdav provider. As of JR 2.16, it started using HC 4.x, which actually started introducing backward incompatibility -- e.g, some HC interfaces/classes have been used in JR webdav API as well, and those had to be changed breaking the compatibility. Therefore, even if commons-vfs's dependency on JR was set to 1.x, it works fine with pre-JR 2.16 versions; as a result, JR itself in v2.14 has a dependency on commons-vfs2 for WebDAV-based DataStore as well, and it works totally fine. In other words, JR-based CMS systems use commons-vfs2 webdav with JR 2.14 now. So, I justified using the old one as jackrabbit2 and the new one as jackrabbit3 [3] by mentioning that the Jackrabbit3 ("OAK") is still using the Jackrabbit API in v2.16+. In other words, Jackrabbit API is also used for "Jackrabbit3" nowadays, and JR itself won't be released in v3 at all since OAK is to replace it as "Jackrabbit 3". Yeah, weird, just figured out a justification. ;-) Regards, Woonsan [1] https://lists.apache.org/thread.html/71dc8ab6526b114fc16f60727ea66ee4c9c4e02dbc10794b5a9477e2@%3Cdev.commons.apache.org%3E [2] https://lists.apache.org/thread.html/2632179eab395e25261f8e55bfebd9d6da9bb72b769a0b56c5b6bfd8@%3Cdev.commons.apache.org%3E
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
