Peter, I've forked the JGDMS project and have started working with it, where do you want me to post questions/comments?
Regards Dennis On Wed, Jun 28, 2017 at 5:24 AM, Peter <j...@zeus.net.au> wrote: > BTW, thanks for writing the script to get it started, it was a huge help. > > Cheers, > > Peter. > > On 27/06/2017 1:32 AM, Dennis Reedy wrote: > >> Hi Peter, >> >> Congrats on all the work you've put into this project. Modularizing the >> project is a big step forward. As you know I've been using Maven for my >> projects, but lately I've found that Gradle provides a much more powerful, >> straight forward and flexible approach for project automation, especially >> for multi-module projects. >> >> You can take a look at what a Gradle project would look like with River >> here (https://github.com/dreedyman/apache-river-example). If you'd like >> I could work with you and see what a Gradle version of JGDMS would look >> like, IMO it will simplify the project greatly. >> >> HTH >> >> Regards >> >> Dennis >> >> Sent from my iPhone >> >> On Jun 23, 2017, at 7:50 AM, Peter<j...@zeus.net.au> wrote: >>> >>> This is what a Maven Build looks like: >>> >>> https://travis-ci.org/pfirmstone/JGDMS/builds/246158857?utm_ >>> source=email&utm_medium=notification >>> >>> All modules are also OSGi bundles, no split packages, no circular >>> dependencies. >>> >>> Yeah even phoenix is still there, no longer dependant on the Sun JVM >>> implementation, can run on any JVM now and uses JERI Endpoints by default. >>> >>> The only remaining component that is Sun JVM implementation dependant is >>> the JERI Kerberos provider. >>> >>> There's even a compatibility library for Jini 2.1, so people can upgrade >>> and migrate their code on their time schedule. >>> >>> All the old ways of using Jini are still supported, such as >>> classdepandjar, preferred classloading, but now Maven and OSGi are much >>> better supported too. >>> >>> Oh yeah, security has been addressed, deserialization with input >>> validation, the latest TLSv1.2 cyphers, IPv6 Global discovery announcement >>> etc. >>> >>> Oh and anyone can build it now, with a simple one line argument. The >>> build also includes CVE security checks. >>> >>> These are the features that were so hard to get acceptance for, but as >>> it turns out, you don't need to break backward compatibility in order to >>> achieve it. >>> >>> This is how I'd like River to be, of course if the community wants >>> something else, then I'll support whatever the community decides. >>> >>> Regards, >>> >>> Peter. >>> >> >
