Mauro, for playing with the plugin I've compiled a tar ball comprising the hellbound-examples like I use them.
The example contains three modules. "hellbound2-app" has got the app-code as well as the behaviour classes (in the test-folder). The second module "hellbound2-behaviours" contains just the behaviours (here in the main-folder) and depends upon "hellbound2-app". The third "..-stories" ...well, I didn't get that far. I failed to run the behaviours either in "hellbound2-app" nore in "hellbound2-behaviours". What I'm after is, how do I get them running? any solution's fine, the simpler the better. Is there something I'm failed to see? Please take at look at them and try to run the plugin (e.g. "mvn verify" will do). If verifying hellbound2-app fails you can still go on to verify "hellboun2-behaviours" by installing "hellbound2-app", then going to "hellbound2-behaviours" directory and run maven again. Do you experience any failures too? Stefan 2007/6/6, Mauro Talevi <[EMAIL PROTECTED]>:
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
hellbound2.tar.bz
Description: application/bzip
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
