RC4 to 1.0 problems

[Ja...@barclayscapital.com]

Great to see 1.0's released.

But sadly I've just downloaded it and am having problems with a build that
worked fine under RC4.  More specifically some of my test cases don't work
any more.

For my sins I'm running on Win2K and my tests require a JNI dll on the path
- the setting up of the path to pick this up is what no longer works.  This
is how my projects are set up, with the relevant project.properties
sections:

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}

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;${basedir}/
../../../../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

My initial thought was that property inhertance had changed in some way, but
even explicitly putting the "maven.junit.sysproperties=..." in
project.properties for either B or C doesn't fix it.  So I can only assume
something's changed with the interaction of the reactor and the test plugin.

Before anyone asks:
1. I have blown away my local cache before running 1.0
2. It works again if I revert back to RC4

Anybody got any ideas?

many thanks

James


------------------------------------------------------------------------
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: RC4 to 1.0 problems

[Dion Gillard <di...@gmail.com>]

On Wed, 14 Jul 2004 11:20:19 +0100, james.shute@barclayscapital.com
<ja...@barclayscapital.com> 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;${basedir}/
> ../../../../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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org