[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mauro Talevi updated JBEHAVE-414: --------------------------------- Fix Version/s: (was: 3.x) 3.4.3 Assignee: Mauro Talevi > Document generating StepDocs from a Embeddable instance > --------------------------------------------------------- > > Key: JBEHAVE-414 > URL: http://jira.codehaus.org/browse/JBEHAVE-414 > Project: JBehave > Issue Type: Task > Components: Core > Reporter: Paul Hammant > Assignee: Mauro Talevi > Priority: Minor > Fix For: 3.4.3 > > > Step Docs pom xml needs an embedder, but not every project is going to have > one. Etsy does not. > Embeddable (EtsyDotComStories) makes an Embedder. Could it expose it for the > StepDoc thingy to leverage? > Alternatively, is it not really the Configuration that is needed by the > reportStepdocs() method that the jbehave-plugin calls ? Could this be more > flexible so that simpler cases that subclass JUnitStories ONLY can play with > stepdocs production ? -- 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