The project will be discussing its future direction after River 3.0 is released.
Tommorrow I will generate updated release artifacts from trunk, it looks like I will need to exclude external jar files from the source release. Whether in its current form could support Android depends on whether Google includes RMI. The community has already removed parts of jrmp and activation from River 2.2.3. So there seems to be little reason to use RMI classes at all. If the community were willing to replace uses of RMI classes and interfaces, then we could cleanly support platforms like android that don't contain rmi classes. While we retain MarshalledObject we still use jrmp. We could create an android version of River that has alternatives to rmi classes and replace those classes in the stream to remain compatible with River as it is. Regards, Peter. Sent from my Samsung device. Include original message ---- Original message ---- From: "Michał Kłeczek (XPro)" <michal.klec...@xpro.biz> Sent: 16/01/2016 07:00:39 am To: dev@river.apache.org Subject: New life for River? I've just came across this: http://arstechnica.co.uk/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/ Hopefully it means we can have River working on Android soon. Michal
