On Oct 27, 2006, at 9:29 AM, Robert Greig wrote:
On 27/10/06, Steve Vinoski <[EMAIL PROTECTED]> wrote:
> not work with Maven?
If it did, I wouldn't have been tearing my hair out over this effort
for the past couple weeks. :-) Basically, even with the suite()
methods in place, maven believes that there are no tests to run.
I believe bug report [1] captures why the suite() approach doesn't
work. My guess is that several of bugs like these combine, with the
result being that the combination of maven and junit4 is simply a
non-
starter.
From the issue http://jira.codehaus.org/browse/SUREFIRE-31 it appears
there is a patch that makes it understand the suite() method. Does
that not work? Or does http://wiki.unto.net/Maven_JUnit4_plugin not
work either?
I don't want to apply patches, as that would mean we'd all have to
manually load the patched version into our local maven repositories.
One idea of maven is to get away from such manual dependency management.
As for the alternate plugin, I already mentioned that previously. It
doesn't work because it simply runs all the unit tests it finds, as
it really should, but since our test subdirs contain unit tests,
system tests, performance tests, etc., failures occur immediately. I
could try to clean up all the tests as I mentioned earlier, but that
job is much bigger than just tweaking the code back to junit3.
--steve
