[
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 am able to reproduce the
problem above. I am using the maven command line client, not the embedded
eclipse maven.
The problem seems to manifest itself only with the maven "site" goal. In this
case the configuration section appears to be more or less inherited from the
maven-surefire-plugin configuration?? This is true at least for the includes
and excludes. I have no idea how this can be, but it is pretty easy to verify.
An "mvn test" runs fine, with configuration data injected as expected.
I think this issue needs to be reopened and looked at, there is definitely
something funny going on here.
> Exclude SCM patterns from ScenarioClassNameFinder
> -------------------------------------------------
>
> Key: JBEHAVE-207
> URL: https://jira.codehaus.org/browse/JBEHAVE-207
> Project: JBehave
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.3
> Reporter: Mauro Talevi
> Priority: Minor
> Fix For: 2.5.6
>
>
> Automatically exclude .svn and other SCM directories from the directory scan.
--
This message is automatically generated by JIRA.
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
