On 9/10/2015 4:37 PM, Peter wrote:
...
Now that the project has decided the only api is net.jini.* it would
seem appropriate to move the org.apache.river.api packages into
org.apache.river.
...

Have we decided that?

In general principle, in order to move forward, we need somewhere to add API that is not part of the Jini standard.

My main agenda is that there should be a clear distinction between what we intend to support long term as API vs. implementation code that can change from release to release.

Reply via email to