[Discuss] Please have a look at the River Container

Hi all: For the past little while, I’ve been working on the Apache River Container (feel free to suggest a better name), which was originally the Surrogate container. I haven’t asked for any help or encouraged collaboration so far (although the project has been in the Apache River repo, so

Re: [Discuss] Please have a look at the River Container

On Feb 18, 2014, at 1011AM, Greg Trasuk tras...@stratuscom.com wrote: By the way, inevitably this container will be compared to Rio and other containers, and someone will ask “Why didn’t you just use Rio (or ‘startnow', or Seven, etc)?” What can I say? I had a different itch to scratch.

Re: [Discuss] Please have a look at the River Container

Hi Dennis: I’ll bite twice: - Your offer to contribute Rio may have been before my time as a committer, because I don’t recall the discussion (mind you I’m also at a loss to recall what I had for dinner last night ;-). How was River unwelcoming, and do you feel the same situation exists

Re: [Discuss] Please have a look at the River Container

On Feb 18, 2014, at 1113AM, Greg Trasuk tras...@stratuscom.com wrote: Hi Dennis: I’ll bite twice: - Your offer to contribute Rio may have been before my time as a committer, because I don’t recall the discussion (mind you I’m also at a loss to recall what I had for dinner last night

Re: [Discuss] Please have a look at the River Container

Hi Dennis: Discussion intertwined… Cheers, Greg. On Feb 18, 2014, at 11:45 AM, Dennis Reedy dennis.re...@gmail.com wrote: On Feb 18, 2014, at 1113AM, Greg Trasuk tras...@stratuscom.com wrote: Hi Dennis: I’ll bite twice: - Your offer to contribute Rio may have been before my

[Result][Vote] (RIVER-432) Jar files in svn and src distributions - Rejected

Simon’s ‘-1’ represents a veto. +1 Peter +1 Greg -1 Simon I will close the JIRA issue. Cheers, Greg Trasuk.

Re: DISCUSS: Proposal for eliminating tensions; return to collaborative development

Hi all : I had originally sent this message on Feb 10, but I noticed today that it wasn’t in the archives. Upon further checking, I realized that I had sent it from the wrong email address (as I sometimes do) and so it got stopped in moderation. My apologies… If history repeats itself, the

Build failed in Jenkins: river-qa-refactor-solaris #20

See https://builds.apache.org/job/river-qa-refactor-solaris/20/ -- [...truncated 7831 lines...] mahalo.jar: [java] Warning: Class not found: au.net.zeus.collection.RC [java] Warning: Class not found: au.net.zeus.collection.Ref [jar]

Re: [Discuss] Accept Rio into River

Greg, Thanks for starting this. On Feb 18, 2014, at 534PM, Greg Trasuk tras...@stratuscom.com wrote: Hi all: Dennis has indicated that he’d be willing to contribute the Rio container to River. Just to be clear, Rio is not just a container (its one small part of it). Rio proves alot

Re: [Discuss] Please have a look at the River Container

I’ll offer my observation from overheard discussions over the years, from a few, but varied Jini community members. But first, let me state that I am a pro Rio person (and Dennis I must apologize again for leaving it off of my slide at the Jini Community meeting in Europe). I’ve never used

Re: [Discuss] Please have a look at the River Container

Greg, FWIW, I agree with you. I find the lack of relative ease of use is the number one adoption inhibitor of Jini, now River. Further, the idea of creating something that is not in the mainstream group thought process will be greeted with lengthy and detailed rationale for why it's not the way

Re: [Discuss] Please have a look at the River Container

Op Di, 2014-02-18 om 21:27 -0500 skryf Dennis Reedy: BTW, I respectfully don't agree with Rio was just an awfully large and complicated bit of code to “start” with. As a user of Rio, and being somewhat familiar with its internal workings, I also have to disagree with that statement.