[ http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216678#action_216678 ]
Mauro Talevi commented on JBEHAVE-254: -------------------------------------- Created separate issue JBEHAVE-265 to track annotation-based configuration. > Review story/steps configuration > --------------------------------- > > Key: JBEHAVE-254 > URL: http://jira.codehaus.org/browse/JBEHAVE-254 > Project: JBehave > Issue Type: New Feature > Components: Core > Reporter: Mauro Talevi > Assignee: Mauro Talevi > Fix For: 3.0 > > > Story and steps configuration should be reviewed to maintain what worked well > and remove what did not. > Criterias for refactor: > - Adopt similar paradigm for story and steps configuration > - Elements of the configuration should always have default values and should > be overridable singularly, after instantiation > - Immutability of configuration can be obtained by decorating a configuration > and disabling the use* methods. > - Default configurations should always be available to runners and should not > be required as parameters in super() invocations. > Changes: > - Have a base abstract class [Story|Steps]Configuration that holds the > elements of the configuration, injectable both via constructor and after > instantiation via use* methods. > - Have a MostUseful[Story|Steps]Configuration that holds the default > configuration that can be used as base for overriding individual elements. > - Have an Immutable[Story|Steps]Configuration throwing an exception when use* > methods invoked. -- 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