jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Bocanegra (JIRA)" <j...@apache.org>
Subject [jira] [Created] (JCR-3612) Contribute Adobe's FileVault to ASF
Date Fri, 28 Jun 2013 00:50:19 GMT
Tobias Bocanegra created JCR-3612:

             Summary: Contribute Adobe's FileVault to ASF
                 Key: JCR-3612
                 URL: https://issues.apache.org/jira/browse/JCR-3612
             Project: Jackrabbit Content Repository
          Issue Type: New Feature
          Components: sandbox
            Reporter: Tobias Bocanegra
            Assignee: Tobias Bocanegra
            Priority: Trivial

Note: This holds as a container bug for all the work needed until the contribution is complete.

We at Adobe (and at Day Software before)
developed quite some tooling around exporting, importing and syncing
content from and to a JCR repository. The "checked-out" structure on
the local filesystem also offers SVN-like operations, like update,
checkin, status, etc., against the JCR repository. We called this
system the "File Vault (vlt)". It uses the built-in JCR remoting of
Jackrabbit to read and write the content.

We also used the same serialization format to implement our "Content
Packages" which basically are a zip of such an exported structure, w/o
all the meta information needed for syncing. This packaging system
also comes with a HTTP service and UI that allows to actually manage
those packages (create, update, install, uninstall, upload, etc).

Additionally we also developed some maven plugins that allow building
such content packages, controlling vlt (the command line tool) and
deploying content packages into a running repository.

Our R&D thinks that the Jackrabbit project would benefit from such
tooling since nothing comparable is established today. We are now at a
stage where we cleared all hurdles with Adobe Legal, and streamlined
the codebase so that we are ready to contribute.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message