We've currently got an org.apache.river.api namespace for new stuff.
I think a rename would need an additional motivator.
At some point, I suspect around Java 8's release, classdep may begin
having issues finding dependencies.
I modified classdep (with help from Tim Blackman) to add support for
generics in order to support Java 5, however classdep has a clunky
antique feel about it now, I think Rio has a good deployment strategy we
could all learn from.
Cheers,
Peter.
On 12/03/2013 8:13 PM, Dan Creswell wrote:
"But I do think we ought to keep the domain reg."
Shouldn't we talk the grand "River rename"? I mean we've said before
now that we'd treat net.jini as an old compatibility namespace and
define some new ones over time....
Just raising a topic, not prosecuting an agenda.
On 12 March 2013 01:39, Greg Trasuk<[email protected]> wrote:
I'm confused - wasn't that domain transferred to the Apache Software
Foundation? And if so, shouldn't the foundation be renewing the domain
registration?
If not, I suspect that we should maintain it simply because our package
name starts with "net.jini". Who currently owns it? I'll chip in to
renew the domain registration, although I'm in agreement that any
content hosting can stop. If it helps, I can host a placeholder page on
my server. But I do think we ought to keep the domain reg.
Cheers,
Greg.
On Mon, 2013-03-11 at 17:52, Peter wrote:
The jini.net domain name registration has come up for renewal again.
I'm wondering if anyone wants to take over as custodian?
Does anyone have any time or ideas to do something useful with jini.net?
Peter.
