[
http://jira.codehaus.org/browse/JBEHAVE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-217:
---------------------------------
Fix Version/s: 2.4
Assignee: Mauro Talevi
Summary: Allow configuration to be overridden (was: Allow
configuration to be set)
> Allow configuration to be overridden
> ------------------------------------
>
> Key: JBEHAVE-217
> URL: http://jira.codehaus.org/browse/JBEHAVE-217
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Reporter: Chris Jensen
> Assignee: Mauro Talevi
> Fix For: 2.4
>
>
> Currently to configure a scenario you need to implement an interface and it
> ties configuration to the scenario author. From what I can see the only way
> to externally override configuration would be to use AOP. This isn't a very
> standard way of doing configuration. It should use public getter and setter
> methods so the configuration can be overridden or extended to, for instance,
> add in a scenario reporter.
> Ideally I should be able to write a Sonar plug-in for JBehave that can run
> existing scenarios and capture their output for presentation within Sonar.
> To make this work for everyone out of the box, I shouldn't need to resort to
> using AOP or to requiring special per-scenario configuration by people who
> want to get nice reporting in Sonar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
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
