For some work I have to frequently launch Sling standalone jar with clean start. The development flow is like
1. Start sling 2. Debug startup logic and initial installation 3. Shutdown 4. Update certain bundles in resources/install folder based on #2. For this install them in Maven first 5. Clean existing sling home directory 6. Repackage Sling standalone so that updated bundle from #4 gets picked up 7. Use the newly created standalone jar In this flow step #6 takes some time (~30-40 sec). To reduce the turnaround time I would like to run the standalone jar in exploded format. So that I can bypass #6 and just update the jar in install folder directly. I tried to run Sling by exploding the standalone jar and explicitly passing Main class in startup. However this does not work as it uses ClassloaderResourceProvider and in that getChilderen() does not work. Is there any other way I can simplify my development workflow such that I can bypass repackaging step #6? Otherwise I was thinking to modify the MainDelgate to uses some sort FilesystemResourceProvider depending on startup mode. Any thoughts/suggestions!! Chetan Mehrotra
