On Monday 26 January 2015 09:39:09 Jeff Young wrote: > I'm in agreement with Justin and Bertrand that the developer (and not the > administrator) is the right person to author this information.
When a team delivers a slightly more ambitious application an admin has to kick in anyway, e.g. to configure service user mapping, security, URL mappings or the like. Configuring the script engines is an admin task in my opinion also (and could be therefore more restrictive). I've updated the issue with our findings so far. Regards, O. > I'm on the fence regarding whether to put it in the file or use a > property. (If we do use a property, it should be inherited so it can be > put on entire sub-trees easily.) > > Cheers, > Jeff. > > On 26/01/2015 09:24, "Bertrand Delacretaz" <[email protected]> wrote: > >On Sat, Jan 24, 2015 at 12:34 PM, Justin Edelson > > > ><[email protected]> wrote: > >> ...Only the developer knows how to map their scripts to the right > >> > >>engine.... > > > >And the developer creates scripts under /apps/foo for project foo, so > >it makes absolute sense to set a sling:script property on /apps/foo to > >indicate a preference for one script engine over another under there. > > > >-Bertrand
