Ok I've had a brief look at debugging failing tests, it's worth noting
that these tests now failing on my machine, passed two months ago with
flying colours.
The really weird part is the failure is in ActivationGroup, it appears
PreferredClassProvider is being given a fully defined class name to load
instead of a codebase url.
It looks like the URI code is doing the right thing, there seems to be
something else going wrong here.
I've increased the verbosity of the MalformedURLException:
Exception in starting ActivationGroupInit:
[java] ActSys-err: 02/11/2012 8:01:16
PM:Group-0:err:java.net.MalformedURLException: URI is not absolute:
com.sun.jini.phoenix.ActivationGroupImpl in path:
com.sun.jini.phoenix.ActivationGroupImpl
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
net.jini.loader.pref.PreferredClassProvider.pathToURIs(PreferredClassProvider.java:1451)
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
net.jini.loader.pref.PreferredClassProvider.loadClass(PreferredClassProvider.java:519)
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:247)
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
net.jini.loader.RiverClassLoader$DefaultRiverClassLoaderSpi.loadClass(RiverClassLoader.java:113)
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
net.jini.loader.RiverClassLoader.loadClass(RiverClassLoader.java:99)
[java] ActSys-err: 02/11/2012 8:01:16 PM:Group-0:err: at
com.sun.jini.phoenix.ActivationGroupInit.main(ActivationGroupInit.java:73)
