[
https://jira.codehaus.org/browse/JBEHAVE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-625:
---------------------------------
Description:
Little language example:
((suite = "smoke" | suite = "regression") & process = "booking")
Groovy closures (http://groovy.codehaus.org/Quick+Start) would be an effective
way to construct an alternate grammar.
It should be a non-default implementation to allow for backwards compatibility.
was:
Little language example:
((suite = "smoke" | suite = "regression") & process = "booking")
It could be that Groovy closures (http://groovy.codehaus.org/Quick+Start) or
Rhino (http://www.mozilla.org/rhino/tutorial.html) could be an effective way to
construct an alternate grammar.
Having this as a plugin -DmetaFilterImplementation might allow for backwards
compatibility too.
Fix Version/s: 3.5.4
Summary: MetaFilter should support meta matching logic written in a
Groovy (was: MetaFilter should support logic written in a scripting language)
> MetaFilter should support meta matching logic written in a Groovy
> -----------------------------------------------------------------
>
> Key: JBEHAVE-625
> URL: https://jira.codehaus.org/browse/JBEHAVE-625
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Reporter: Paul Hammant
> Assignee: Paul Hammant
> Fix For: 3.5.4, 3.6
>
>
> Little language example:
> ((suite = "smoke" | suite = "regression") & process = "booking")
> Groovy closures (http://groovy.codehaus.org/Quick+Start) would be an
> effective way to construct an alternate grammar.
> It should be a non-default implementation to allow for backwards
> compatibility.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
