[ http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216912#action_216912 ]
Mauro Talevi commented on JBEHAVE-265: -------------------------------------- The issue I see in approach 1 is the tie-in with JUnitRunner, which works fine in IDE but we'd need to change the command-line runner. This may not be a bad thing, we may decide to leverage the JUnit runner for command-line too. I think it's important to have configuration mechanism that are valid in IDE as well as command-line. > Allow annotation-based configuration > ------------------------------------ > > Key: JBEHAVE-265 > URL: http://jira.codehaus.org/browse/JBEHAVE-265 > Project: JBehave > Issue Type: New Feature > Components: Core > Reporter: Mauro Talevi > Fix For: 3.0 > > > Annotations-based configuration can be preferable to some users. > Investigate and implement annotation-based alternatives to programmatic > configuration, which should always be possible. -- 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