Re: Release 3.0

> On Sep 3, 2015, at 3:43 AM, Peter wrote: > > +1 for putting it in the net.jini.config API namespace, the DSL lives in > net.jini.config. Arguably, the important thing, the thing that really _should_ be in net.jini.config, is the Configuration interface., bakes that forms

Re: Release 3.0

+1 on a short path to a 3.0 release. Everything else can go into a backlog for 3.1+. Bryan Bryan Thompson Chief Scientist & Founder SYSTAP, LLC 4501 Tower Road Greensboro, NC 27410 br...@systap.com http://blazegraph.com http://blog.bigdata.com http://mapgraph.io

Re: Release 3.0

I think that we could: 1. Release 3.0 on the shortest path consistent with appropriate QA. 2a. Refactor the project structure into modules 2b. Extend the project into interesting use case areas (IoT was discussed recently). 2a and 2b could occur in parallel. A release with a project modular

Re: Release 3.0

> On Sep 3, 2015, at 203PM, Bryan Thompson wrote: > > I think that we could: > > 1. Release 3.0 on the shortest path consistent with appropriate QA. > 2a. Refactor the project structure into modules > 2b. Extend the project into interesting use case areas (IoT was discussed >

Re: Release 3.0

Spinning off a 2.2.2 modularization effort to me sounds like it could create some confusion and undermine the 3.0 release. I'd rather focus the modularization effort into 3.0. Modularization is a huge pain and the payoff is long term. Rather not pay it twice. Yes. Big ant projects with checked

Re: Release 3.0

> On Sep 3, 2015, at 218PM, Bryan Thompson wrote: > > Spinning off a 2.2.2 modularization effort to me sounds like it could > create some confusion and undermine the 3.0 release. I'd rather focus the > modularization effort into 3.0. Modularization is a huge pain and the >

Re: Release 3.0

Hi Greg, Thanks for the reply, see below. > On Sep 3, 2015, at 126PM, Greg Trasuk wrote: > >> >> I am considering your point wrt creating a separate project, I warming up to >> it, but I would really rather see River split into a multi-module project >> instead of

Re: Release 3.0

+1 for putting it in the net.jini.config API namespace, the DSL lives in net.jini.config. This is a good thing, we should consider deprecating the DSL in favour of Groovy. There's no standards body for Jini standardisation, we need to be able to manage and evolve our API sensibly, locking

Re: Release 3.0

Dennis, We're still missing the following package from the qa test suite: org.apache.river.test.support.* I've added it locally and now the qa test suite is running, I'll report back my results. Regards, Peter.