Re: [xwiki-devs] [Proposal] Extension Manager

On Sun, Jun 21, 2009 at 4:58 AM, Vincent Massol &lt;vincent(a)massol.net&gt; wrote: Re state snapshot of versions we want to do this but with the new model/storage using JCR. See http://dev.xwiki.org/xwiki/bin/view/Design/XWikiModel20 [...] I don't think this is related to the extension manager which role should be to import/export XARs. Whether the XAR is built from SVN or some other mechanism is independent IMO. [...] Again for me this is about implementing a storage based on SVN. When we have JCR support all we'd need is a JCR implementation for SVN (I looked some time ago and couldn't find one though). alongside xwiki's existing versioning system (not replacing it). It reuses existing social practices and implementations associated with the delivery of packaged software products (or websites) out of a branched repository. The application manager would subsume and hide the implementation details, and simply make it easy to snapshot a whole set of documents that comprise a release (each at a particular xwiki revision number) and make that snapshot "open" to anything that can talk to subversion on the back-end. For example, Xwiki.org&com has clearly found benefit from having a release process based on branches in subversion. And there are a number of scripts used to automate the generation of a "build" and various releases for Xwiki from the repository. It would be nice to be able to replicate this "type" of process, for websites, for spaces, or packages of Xwiki documents. But without exposing much underlying details of the back-end revision control system -- and a nice and simple UI to drive it all as a "one click" process. What I was suggesting is that this kind of bigger-picture use-case be considered in the application-manager. In other words, change "I don't think this is related to the extension manager which role should be to import/export XARs. Whether the XAR is built from SVN or some other mechanism is independent IMO." to "Using a 'branched release' model be able to import/export XARs. This implementation is entirely Independent of Xwiki's underlying storage (therefore future compatible with WikiModel20<http://dev.xwiki.org/xwiki/bin/view/Design/XWikiModel20>)0>), and probably implemented as an independent application that talks REST/HTTP to Xwiki, and makes direct use of an existing subversion repository as the back-end. For compatibility with the widest number of tools, and in order to reuse as much code as possible, this application-manager-application (separate app from the Xwiki instance being "managed") would make use of an existing, standard, instance of a subversion repository (e.g. implemented via apache httpd) and work alongside standard access-control and authentication mechanisms used for the repository." Niels http://nielsmayer.com