Hi, On Wed, Mar 20, 2013 at 1:31 PM, Fabian Christ <[email protected]> wrote: > ...The stuff in /apps can be packaged as an OSGi bundle and by this > versioned like any other software component. It can also be easily > deployed...
You mean versioned in your source code tree, right? > ...The stuff in the JCR (which is the RESTful interface) is different. > How should I handle this on deployment to another machine? How is > versioning supported here?... Sling provides a way to embed initial content in bundles [2], that is installed in the repository when the bundle is activated. The Slingbucks sample [1] does have such content under src/main/resources/SLING-CONTENT for example. This means your initial content can live in your source code repository alongside whatever goes under /apps. You're right that CQ5 for example adds a content package manager on top of Sling, which makes distributing JCR content easier - but I think the Sling initial content mechanisms should work as well, at least for setting up the base content that your application needs. Would that initial content mechanism work for you, or what are you missing? -Bertrand [1] https://svn.apache.org/repos/asf/sling/trunk/samples/slingbucks [2] http://sling.apache.org/site/content-loading.html
