Hi Robert,
the Maven testClasspath automatically includes the compileClasspath for
a given project.
If you send us a Maven pom.xml reproducing the (un)desidered behaviour
we can help you investigate the issue.
Cheers
On Wed Dec 14 15:08:40 2011, Robert Boothby wrote:
I've been working to integrate JBehave 3.5.4 with a client's existing Maven
3.0.3 project...
I decided to use the test scope to be able to run BDD acceptance criteria
directly against certain elements of the code, but test scope does not handle
class paths like I would expect.
It appears to solely use the maven project test dependencies and not include
the non-test dependencies. This appears to come from the AbstractEmbedderMojo
using exclusive OR logic when setting up the Embedder class loader. I would
have expected test scope to use both the compile and test Maven class paths.
Am I missing something? Is there a correct way to do this?
Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
