On Sat, Apr 4, 2015 at 7:19 PM, Radu Cotescu <[email protected]> wrote: > Hi, > > Given the recent improvements of the Sightly implementation from Sling I > think that having this scripting engine in the launchpad would be a nice > feature.
Sounds OK to me, as long as we don't introduce SNAPSHOT dependencies, as they will not be buildable in the same reactor. Wouldn't it be clearer though to move sightly and all its dependencies to /bundles/? I have a documented uneasy feeling about tangled dependencies between our reactor builds. Cheers, Robert > > What are the requirements for including Sightly into the launchpad? The > following would be the list of bundles that need to be added > to launchpad/slingstart/src/main/provisioning/sling.txt: > > # xss > javax.mail/mail/1.4.7 > org.apache.sling/org.apache.sling.xss/1.0.2 # contrib/extensions/xss > # i18n > org.apache.sling/org.apache.sling.i18n/2.3.2 # contrib/extensions/i18n > # jcr compiler > org.apache.sling/org.apache.sling.jcr.compiler/2.1.0 # contrib/jcr/compiler > # sightly > org.apache.sling/org.apache.sling.scripting.sightly/1.0.0 > #contrib/scripting/sightly > org.apache.sling/org.apache.sling.scripting.sightly.js.provider/1.0.0 > #contrib/scripting/sightly > org.apache.sling/org.apache.sling.scripting.sightly.repl/1.0.0 > #contrib/scripting/sightly > > Cheers, > Radu -- Sent from my (old) computer
