this question comes up so frequently, and the answer is always, "Junit tests should be forked." Can someone PLEASE change the default behavior of the test plugin to fork unless it's overridden? It would save on the constent confusion in this area.
-----Original Message----- From: Julien Kirch [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 3:21 PM To: Maven Users List Subject: Re: problem *not* forking unit tests Hi Micah I think the test forking law is "thou shall fork", not forking is a real classpath mess between maven and project classpath (and caused your problem), I don't think not forking is ever a good idea. Julien Micah Craig wrote: > Hi, > I just upgraded from rc1 to 1.0.1, and suddenly, I can't run JUnit > tests un-forked (maven.junit.fork=no). Failure output is below. Could > this be some sort of mangled classpath issue left over from the upgrade, > or is something more sinister afoot. Thanks, > > -micah --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
