Stefan Hübner wrote:
So this would boil down to placing behaviours/stories either in
"src/main/java" or "src/test/java" and scoping jbehave either in
compile or test scope.
The switch could be easily supported by a simple boolean configuration
option, I guess. The plugin then would create a classloader upon
either compile scope or test scope classpath elements.
Yep - and that can be accomplished with current impl, I believe.
All that matters is to make the classpath elements javadoc property settable
via the pom.
I still need to convince myself of the best approach in this regard.
I don't see "hyper-isolation"
in classloading as necessarily a significant advantage - especially if
offset against other cons or
complications. The current approach is quite simple and configurable
- it takes the libs configured
in a given maven scope and builds a classloader with them. I'll give
it more thought.
Fine. I'll those two classloader approaches a try in different scenarios.
Fine - let's evaluate pros and cons.
Since we're talking about Maven2 support, may I also suggest to update
jbehave's parent- and core-poms? The dependencies should be mentioned
properly. This would help developers great deals.
The parent has no dependencies. The core deps will be added - you're right.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
