The iiop tests passed, so I assume that means the stubs compiled.
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_BehaviorTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_BehaviorTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_BehaviorTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_ExportExceptionTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_ExportExceptionTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_ExportExceptionTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_IllegalStateExceptionTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_IllegalStateExceptionTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_IllegalStateExceptionTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_NullPointerExceptionTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_NullPointerExceptionTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_NullPointerExceptionTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_InvocationTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_InvocationTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_InvocationTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_BehaviorTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_BehaviorTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_BehaviorTest2.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_IllegalStateExceptionTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_IllegalStateExceptionTest1.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Unexport_IllegalStateExceptionTest2.td
Here’s a portion of the output from ‘ant -v iiop.stubs’:
iiop.stubs:
[rmic] com/sun/jini/test/spec/iiop/util/TestRemoteObject.class omitted as
/home/pi/river-2.2/qa/build/classes/com/sun/jini/test/spec/iiop/util/_TestRemoteObject_Tie.class:/home/pi/river-2.2/qa/build/classes/com/sun/jini/test/spec/iiop/util/_TestRemoteInterface_Stub.class
are up to date.
So, yeah, seems to work. The rpi jdk is a full Java SE jdk, it just doesn’t
support server mode on the pi, I’d guess mainly because the raspberry pi only
has 512MB RAM. Here’s the error message that it prints when you invoke
‘-server’.
> pi@raspberrypi ~/river-2.2/qa $ java -server -version
> Error occurred during initialization of VM
> Server VM is only supported on ARMv7+ VFP
Cheers,
Greg Trasuk
> On Jan 5, 2016, at 6:21 PM, Peter <j...@zeus.net.au> wrote:
>
> Just curious, were you able to compile iiop stubs, or did you find that this
> wasn't supported by the arm jdk
>
> Regards,
>
> Peter.
>
> Sent from my Samsung device.
>
> Include original message
> ---- Original message ----
> From: Greg Trasuk <tras...@trasuk.com>
> Sent: 06/01/2016 02:37:39 am
> To: dev@river.apache.org
> Subject: Testing the 2.2 branch on Raspberry Pi
>
> Just to close the loop on this after taking out the ‘-server’ option on the
> JVM, the integration tests passed.
>
> [java] -----------------------------------------
> [java]
> [java] # of tests started = 1310
> [java] # of tests completed = 1310
> [java] # of tests skipped = 40
> [java] # of tests passed = 1310
> [java] # of tests failed = 0
> [java]
> [java] -----------------------------------------
> [java]
> [java] Date finished:
> [java] Tue Jan 05 12:48:28 UTC 2016
> [java] Time elapsed:
> [java] 101262 seconds
> [java]
>
> collect-result:
> [copy] Copying 1 file to /home/pi/river-2.2/qa/result
> [copy] Copying 1 file to /home/pi/river-2.2/qa/result
> [zip] Building zip:
> /home/pi/river-2.2/qa/result/qaresults-arm-Linux-1.8.0.zip
>
> pi@raspberrypi ~/river-2.2 $ java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build 1.8.0-b132)
> Java HotSpot(TM) Client VM (build 25.0-b70, mixed mode)
>
> pi@raspberrypi ~/river-2.2 $ uname -a
> Linux raspberrypi 3.18.11+ #781 PREEMPT Tue Apr 21 18:02:18 BST 2015 armv6l
> GNU/Linux
>
> Cheers,
>
> Greg Trasuk
>
>
>
>
