|
[
Permalink
| « Hide
]
Jean-Laurent de Morlhon added a comment - 16/Feb/06 07:05 AM
this is still happening with a fresh build of the plugin with svn at revision 1496
what part of the site is failing? surefire-report, or cobertura, or something else?
And what are your effective <surefire> settings for each artifact.
The variable is readonly, and the configuration may be errorneous? OK, I'm trying to run StrutsTestCase with Maven 2.x and need the web.xml and struts-config.xml to be in the classpath, which they are not by default.
So, I have the following configuration for the surefire plugin: <plugin> Any ideas? I've created a patch against revision 450675 which fixes this issue and allows you to specify additional classpaths:
<plugin> This patch does pretty much the same thing as the one supplied in MSUREFIRE-153 but I can't understand why that one hasn't been applied. I'm using this for now. I don't want to patch core maven I've done this before and it leads to a maintenance headache. For now I am running Junit via the ant plugin but this is not the point of maven. Please can we get this into the core asap.
Cheers Fixed and integration tested in revision 597783.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||