Building River on Windows (XP) and running the QA tests works fine ... No
new ground is being broken there.
There are a couple things to watch out for, though:
1. make sure the JDK you are using is installed in a path without spaces
(e.g. C:\Java)
2. make sure you checkout River in a path without spaces (e.g.
C:\Projects\River)
3. make sure the Ant you are using is using the JDK from (1) -> you can run
"ant diagnostics" in the project directory to find out
4. when using an IDE to build, make sure this IDE runs on the JDK from (1) -
you can configure this for Netbeans in <netbeans_home>/etc/netbeans.conf -
and the Ant from (3)
Especially running the QA test suite will not work when the above is not
taken into account.
But if it is, you'll see:
-----------------------------------------
GENERAL HARNESS CONFIGURATION INFORMATION:
Date started:
Tue Aug 17 00:19:16 CEST 2010
Installation directory of the JSK:
com.sun.jini.jsk.home=C:\Projects\river-trunk
Installation directory of the harness:
com.sun.jini.qa.home=C:\Projects\river-trunk\qa
Categories being tested:
categories=id loader policyprovider locatordiscovery activation config
discoverymanager joinmanager url iiop jrmp reliability thread
-----------------------------------------
ENVIRONMENT PROPERTIES:
JVM information:
Java HotSpot(TM) Client VM, 17.0-b17, 32 bit VM mode
Sun Microsystems Inc.
OS information:
Windows XP, 5.1, x86
.........
-----------------------------------------
# of tests started = 397
# of tests completed = 397
# of tests skipped = 18
# of tests passed = 397
# of tests failed = 0
-----------------------------------------
Date finished:
Tue Aug 17 02:50:48 CEST 2010
Time elapsed:
9092 seconds
BUILD SUCCESSFUL (total time: 151 minutes 34 seconds)
Best
Jonathan
2010/7/16 Peter Firmstone <[email protected]>
> Just a lack of time, I've made some attempts to set up a dev environment on
> Window's Vista, but ran into some problems getting it set up right.
>
> We've considered making a separate release of the qa tests, this would
> assist by checking binary compatibility is maintained, eg method signatures
> etc.
>
>
> Cheers,
>
> Peter.
>
> Patricia Shanahan wrote:
>
>> I'm a little concerned about the implications of my difficulties running
>> the River jtreg tests in a WindowsXP environment. I seem to be breaking new
>> ground, but I feel a full test on at least one of the MS-Windows operating
>> systems should be part of the release process, to guard against e.g.
>> dependence on a single rooted file system getting built in to River.
>>
>> Is there some reason against doing so, or just a lack of resources?
>>
>> Patricia
>>
>>
>
