Another vote for using org.apache.river everywhere - if it's not called Jini from a branding perspective, it shouldn't be in the code (yet another thing that adds cognitive overhead).
3.0 is not backwards-compatible in anyway, right? So may as well force a package name change. I know I'm going to regret that when I have to refactor my own code base, but it's probably for the best :-) regards, Dawid Loubser On 01/09/2015 03:41, Patricia Shanahan wrote: > On 8/31/2015 4:07 PM, Bryan Thompson wrote: > ... >> Why use net.jini.* rather than net.river.*? > > Do mean "net.river" rather than "org.apache.river"? > > We have domain names jini.net and river.apache.org, and can base > package names on either of those. If we want to use anything else, we > would need to acquire the corresponding domain name. > > In my opinion, for branding reasons, we should use org.apache.river.* > wherever possible.
signature.asc
Description: OpenPGP digital signature
