On Fri, May 31, 2013 at 2:08 PM, Robert Munteanu <romb...@apache.org> wrote: > ...I'm frankly more of an IDE guy than a VLT guy from a development > experience point of view....
IMO focusing on filesystem operations (which can be driven by IDEs) would be the right abstraction level, so that people can use any suitable development environment. Do we need anything more than the following story? ** Life of a Sling Developer ** I have a Sling project at /P on my disk, consisting of Sling resources content and Java bundles code. To start working on it I can point Sling to file:///P, and the content and (Maven-built) bundles are loaded into Sling. I can modify the properties of the Sling /content/foo resource by editing a /P/content/foo/SLING.properties file. Changes to those files are synced quickly to the Sling repository. Changes to Java bundles code under /P are detected (maybe by a separate tool) and cause a rebuild and update of the corresponding bundle. When I'm happy with my content and code, Maven plugins allow me to package it for distribution, as Sling bundles that include initial content. A separate tool allows for dumping a set of Sling repository subtrees as content .properties file. -Bertrand
