Dan North wrote:
Can we make the default constructor chain to the classloader one with a
suitably inoffensive classloader? This would keep Maven happy and mean
people didn't have to inject unnecessary classloaders. Oh man, I love
Java and its funny classloader ways :)
The issue here is that if you want to run scenarios with Maven you need
to provide classloader parameter in the constructor or else the
instantiation will fail. If you provide a default (eg the thread
context classloader) it will not work for Maven (but it will in IDE, for
example).
Best solution is to provide both constructors - and all are happy.
Always happy to consider other solutions though. Let's bang some heads
for 2.2 - since we already have container support to deal with, and that
already has shown several classloading woes.
Anyway, for now I've updated static reference documentation to include a
page for developing scenarios in which the "contract" for scenarios are
outlined.
Dan - can you please upload the docs contained in
http://repository.codehaus.org/org/jbehave/jbehave-distribution/2.1/jbehave-distribution-2.1-bin.zip
to a URL such as
http://jbehave.org/documentations/reference/2.1
or somesuch that makes sense and plays well with wordpress.
The reference docs also include javadocs, which would be handy to have
online.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
