On Wed, Aug 27, 2014 at 3:35 AM, Tim Boudreau <[email protected]> wrote:
> probably starting from a "friend" API. For example, NetBeans tried a > convention of "org.netbeans.api.*" for modules with public API, and > "org.netbeans.modules.*" for non-api stuff, but today you'll find plenty of > modules that have public APIs yet are named "org.netbeans.modules.*" > because their author couldn't predict a priori that there would eventually > be an API. > To be fair, this problem exists in NetBeans because a module is the unit that can be updated, so you can't rename a module a user might already have or they can wind up with two versions of the same package trying to coexist, with potentially nasty consequences. That may be a non-issue here. -Tim
