[jbehave-dev] [jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2009-12-22 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203808#action_203808 ] Mauro Talevi commented on JBEHAVE-207: -- Actually, the Ant DirectoryScanner already has the SCM

[jbehave-dev] [jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2010-05-09 Thread Bogdan Prishedko (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220570#action_220570 ] Bogdan Prishedko commented on JBEHAVE-207: -- This issue reproduces stable if we have sectio

[jbehave-dev] [jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2011-02-03 Thread Marc Siramy (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253978#action_253978 ] Marc Siramy commented on JBEHAVE-207: - Hello, I can reproduce that bug with my plugin configura

[jbehave-dev] [jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2011-12-01 Thread Michael Berg (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284684#comment-284684 ] Michael Berg commented on JBEHAVE-207: -- Using maven 3.0.3 and jbehave-maven-plugin 3.5.3, I a

[jbehave-dev] [jira] Commented: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

2011-12-03 Thread Mauro Talevi (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284810#comment-284810 ] Mauro Talevi commented on JBEHAVE-207: -- Please open a new jira issue, and if possible add a m