Hi Dominik, On Wed, Jan 8, 2014 at 11:34 AM, Dominik Süß <[email protected]> wrote: > ...Sling currently is based on > bundles with the initial-content or installing it from the repo from > install folders. In Adobe CQ Packages (vlt - contributed to Apache some > months ago) are the mechanism to package deployments. So there are multiple > ways to organize deployments. Bug e.g. all are tight to a JCR Repository as > soon as it comes to content (since there is no generic equivalent to the > JCR Installer)...
The OSGi installer can take configs and bundles from the filesystem already, and implementing a provider that uses a Git repository as its source might be interesting w.r.t. devops. >... what doesn't feel right is that the prefered way of > deployment in a Sling based app as Adobe CQ is different from how Sling is > doing deployments with the own parts or demo apps (creating a uncessessary > learning barrier)... Agreed - historical reasons I guess, not sure how we can improve that. -Bertrand
