You need to read the docs on the test plugin. In particular, http://maven.apache.org/reference/plugins/test/properties.html
On that page look for maven.junit.sysproperties. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ "Julien Ruaux" <[EMAIL PROTECTED]> wrote on 15/08/2003 12:00:14 AM: > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
