[
http://jira.codehaus.org/browse/JBEHAVE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261528#action_261528
]
Edward Staub commented on JBEHAVE-218:
--------------------------------------
I agree with Chris, based on my own pain - some English text would help here.
>> But the "test" scope is also configurable.
If by "scope" you mean the test directory, I don't think so.
See [JBEHAVE-454|http://jira.codehaus.org/browse/JBEHAVE-454].
>> The examples (especially the trader one) already present documentation of a
>> typical and suggested Maven usage.
I strongly disagree with the overall documentation philosophy that "examples
are all that's needed". The reader often can't understand "why" in examples -
or worse, infers intent where none existed.
In the current case, the examples show the story code being mixed in the same
source tree with the production code. I don't get this at all - is the intent
to ship the story code as part of the production jar, or "exclude" it, or
something else? This is very idiosyncratic. From the lack of an exclude in
pom, I'd guess that the intent is to just bloat the production jar. Of course,
this all means that unless some dynamic binding is used, the production compile
dependencies have to include all the dependencies for the test code.
I'm probably way off the mark here - but that's my point! If the intent isn't
stated, I'm left to guess - often badly.
> Standardize and make file/directory layout configurable
> -------------------------------------------------------
>
> Key: JBEHAVE-218
> URL: http://jira.codehaus.org/browse/JBEHAVE-218
> Project: JBehave
> Issue Type: Improvement
> Components: Maven Plugin
> Reporter: Chris Jensen
>
> The maven plug-in for JBehave works all right, but it should default to
> standard maven archetype layout for test classes and the JBehave team should
> come up with a standard on where plain-text scenarios should live, what file
> extension they should have (to make them discoverable) and then allow that
> standard to be overridden.
> The documentation on the JBehave site should clearly present the standard
> layout and specify how it can be overridden.
> Reporting output should be included in the standard and should by default go
> where maven reports typically go, in a sub-directory of target.
--
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
