On 6 Mar 2014, at 11:23 pm, Rob Platt <momentum...@gmail.com> wrote:
> > Adam Murdoch wrote: > > possibly DefaultJsEngineRegistry should search for a compatible engine in > > the order that they are added to the registry, and instead do the ordering > > in EmbeddedJsEnginePlugin for the embedded engines only. This way, the user > > can tweak the search order in the registry. > > No problem. Would this then be determined by the order in which the plugins > are listed, or does the user adjust it some other way? The idea is that the plugin order determines some default engines in some default order if the user does not specify any engines. If the user specifies some engines, then no defaults are applied and we use only those engines specified by the user and in the order specified. Thinking about it, we could possibly order the engines if we’re using the defaults, but not if the user has specified any engines. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
