Hello,
Michael Warres identified a number of issues with class loading and
codebase annotation loss, none of which were fully addressed.
https://dl.acm.org/doi/pdf/10./1698139
I wanted to share with you an new JERI InvocationLayerFactory I've been
working on, on and off for some time.
Thanks Dan. :)
On 5/21/2020 12:20 PM, Dan Rollo wrote:
Hi Peter,
I acknowledge the contributions are slow to come, but I agree with your
observation that contributions are still coming. I would prefer the River
project not be moved to the attic just yet. (“I don’t want to go on the cart. I
Thanks Patricia,
I'm not sure we're going to see a significant number of developers
contributing in the near future.
Unfortunately the technical matters, which are complex and difficult
have caused a lot of argument in the past and have been the cause of a
high barrier to entry for new
Hi Peter,
Some quick late night thoughts ...
- Time depending, helping a Gradle build for River is something that I'd
be glad to participate in. I think one of the biggest challenges will be
getting the testing framework working, or choosing a modern equivalent.
- As it relates to
Hi Dennis,
Good to hear from you.
The truth is, I'm no build expert, Dan is much more capable than I am,
so I'm waiting to hear Dan's opinion on Gradle, it certainly looks good.
Would you be interested in helping to create a Gradle build?
Something else I've been thinking about is you once
I think showing/explaing how River can fit into a larger eco-system of
existing applications would certainly help. How could River augment Spring
Boot? What would it look like to combine River and Kafka? A discussion of
what it would mean to deploy micro-services built with RIver in the cloud?
I think engagement requires a few things. +1 on the technical points that
you have called out Peter. But we also need to engage developers beyond
those who are traditional users of River/Jini to foster new development
with River. Which can then lead to new development of River by a broader
base
