JCR-4401: Separate jackrabbit-standalone-components from jackrabbit-standalone #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a new submodule, jackrabbit-standalone-components, which contains most of the dependencies and classes and resource, while jackrabbit-standalone includes all of those transitively through jackrabbit-standalone-components.
I've used this, jackrabbit-standalone-components in the new
webdav4
provider of Commons VFS. Everything seems working fine now. I made a pull request there for review purpose for now: apache/commons-vfs#52By the way, I've made two changes in the standalone
Main
class for the cases where unit tests starts a Jackrabbit standalone Main:#run
public, so unit tests can easily instantiate and start it.#shutdown
as public, so unit tests can make a graceful shutdown before JVM shutdown hook takes the place.