Try this: <j:set var="maven.junit.sysproperties">myprop.1 myprop.2</j:set>
where the myprop.* properties are ones you want junit to see (you can have more than two). Put this line someplace before your unit tests get invoked. I do it in my test:test preGoal. Jeff On Thu, 14 Aug 2003, at 16:00:14 [GMT +0200] Julien Ruaux wrote: > It does, thanks. > But all the system properties I either set in build.properties or on the > command line with -D are bypassed. Any idea ? > -----Original Message----- > From: Jefferson K. French [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 14, 2003 2:37 PM > To: Maven Users List > Subject: Re: Boot classpath > Does setting > maven.junit.fork = true > in your build.properties help? > On Thu, 14 Aug 2003, at 11:09:43 [GMT +0200] Julien Ruaux wrote: >> Hi, >> I am facing a problem with the boot classpath set up by maven. Indeed >> Maven apparently adds xerces.jar to the boot classpath, thus >> preventing my tests from running in the same context as with Junit >> textual runner. In the former the Xerces XML parser is used, in the >> latter Crimson (from >> JDK1.4) is used. What can I do to solve that issue ? >> Thanks, >> Julien -- mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
