1) once. fixed.
2) that's a known issue on a number of recently published sites. It's
in JIRA to fix.
3) there aren't 20 bugs open, half of those are feature requests.
There were no known issues when the last release came out - some have
been raised since then. I'll have to investigate the bug, but the
default is now also childDelegation=false which is the "default
classloading mechanism".
- Brett
On 30/05/06, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
Hi,
1) what is the default forkmode in surefire? The documentation does not seem
to be correct:
forkMode *(Optional)* String ${forkMode} once Option to specify the
forking mode. Can be "never" (default), "once" or "always". "none" and
"pertest" are also accepted for backwards compatibility.
The 3rd column says that "once" is the default, however, the last column
says that "never" is the default. What is correct?
2) The "issue tracking" report points to http://jira.codehaus.org/browse/MPA,
not to http://jira.codehaus.org/browse/MSUREFIRE
3) Is there a way to have surefire use the default classloading mechanism
via some option (mainly to work around
http://jira.codehaus.org/browse/MSUREFIRE-115) -> I would like to migrate to
Maven 2, but this stops me from doing so. I could live with the fact that
the site or something would not work, but I really need to be able to run my
unittests. I was a bit surprised to see about 20 bugs open on one of the
most important plugins of maven.
regards,
Wim
--
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
