[JCR-4401] Split jackrabbit-standalone to jackrabbit-standalone-components and the rest

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.19.0
• Fix Version/s: 2.20, 2.19.2
• Component/s: jackrabbit-standalone
• Assignee: Woonsan Ko
• Reporter: Woonsan Ko
• Created: 08/Jan/19 05:14
• Updated: 18/Oct/19 10:17
• Resolved: 17/Mar/19 22:22

Description

I'd like to help fix VFS-686 [1] by upgrading JR dependency from 1.6.5 to the latest of 2.x for the WebDAV vfs provider. The fix will allow to use WebDAV DataStore backend again. (Since JR upgraded httpclient to v4.x, WebDAV backend has been broken.)

One problem is that the test case for WebDAV vfs provider counts on jackrabbit-standalone dependency-to start an extended JR Main for testing-which has been unavailable in maven repos for long time. It's understandable not to deploy the module as it's too big.
At the same time, it would be awkward if VFS should contain all the necessary JR dependencies as jackrabbit-standalone does.

I think it would be nice if we split the module, by moving all the Java classes and resources with most dependencies, except of jackrabbit-webapp, to a new maven module (e.g, "jackrabbit-standalone-components") and having dependency on this new module and webapp module in jackrabbit-standalone bundle module. This will let VFS keep the JR dependencies simple and easy.

[1] https://issues.apache.org/jira/browse/VFS-686

Issue Links

• is depended upon by: VFS-686 Upgrade Jackrabbit dependency to the latest 2.x
• relates to: JCR-4491 Upgrade Commons VFS to 2.6