I see - I was just going with a solution someone submitted to the list for
the JNI path problem.
So what would the correct syntax be in this case? For arbitrary user
properties the example on that page makes sense, but when it's a
fundamental system property (like java.library.path) then surely it won't be
picked up from my project.properties?
Certainly when I try this it doesn't work:
maven.junit.sysproperties=java.library.path
java.library.path=${maven.tcw.path}
James
-----Original Message-----
From: Dion Gillard [mailto:[EMAIL PROTECTED]
Sent: 14 July 2004 12:02
To: Maven Users List
Subject: Re: RC4 to 1.0 problems
On Wed, 14 Jul 2004 11:20:19 +0100, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> A:
> maven.tcw.path=${basedir}/../../../../Release/bin;${java.library.path}
> ;${bas
> edir}/bobbins
> maven.junit.fork=true
> maven.junit.sysproperties=java.library.path=${maven.tcw.path}
maven.junit.sysproperties is a list of the names of properties to pass, not
the names and values. See
http://maven.apache.org/reference/plugins/test/properties.html
> B: (Extends A, somewhere else in the file system, hence the need to
> redefine the property value)
> maven.tcw.path=${basedir}/../../../../../fo_tcw_core/Release/bin;${bas
> edir}/
> ../../../../Release/bin;${java.library.path};${basedir}/bobbins
>
> C: (Extends B, is in subdirectory of B)
> <nothing>
>
> Now under RC4 the tests run fine, whether I run them from B using the
> reactor, or from C on it's own
>
> But under 1.0 the tests only work when run inside C. Running via the
> reactor fails. Having amended the code to spit out java.library.path,
> in the case where it runs under the reactor then it's just set to my
> standard windows path, i.e. the maven.junit.sysproperties doesn't seem
> to have taken effect
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
