We just need to consider the bootstrap. IIRC, I removed testing from
the bootstrap and left that for the Maven enabled rebuild which will
use the binary plugin so should be fine.
If we agree there was consensus on that other topic, before changing
it, we should make sure it is documented as
I have no idea what I'm going to tackle at this point. I've got a
couple days so I'll do what I can. I just want to get it out as it
seems to be a popular request by users.
I'll start tomorrow by taking a look at JIRA, prune issues down for
the next version and if anyone disagrees they can
Jason,
...
It will take me a couple days to look at the code
and patches that are around.
I assume junit4 is out of scope here (due to java 1.5 requirement)?
In case you will look at MSUREFIRE-109, seems like we where hit by
this last week, so I will have a look at this more closesly (maybe
Awesome!
Does what you said earlier mean that you intend to hook up more of the unit
tests (like the old integration tests under the maven-surefire-plugin dir )
into the core surefire build? If so, please feel free to count on support
from me on making sure the TestNG portions are handled as well
On 24 Sep 06, at 4:39 PM 24 Sep 06, Jesse Kuhnert wrote:
Will tomorrow be too late to send in a tiny set of outstanding
patches for
surefire before you do that?
Nope, I'll just be getting started this week so I doubt it will be
released this week. It will take me a couple days to look at
Will tomorrow be too late to send in a tiny set of outstanding patches for
surefire before you do that?
On 9/24/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
This seemed to be the general consensus with some of the other
project setups like Archetype where all the code is together: the
core, all
This seemed to be the general consensus with some of the other
project setups like Archetype where all the code is together: the
core, all modules and the Maven plugin. I'm going to start working on
the release of the surefire plugin so I figure I might as line put
all the surefire code in