On Fri, Aug 2, 2019 at 4:52 AM Neil C Smith <[email protected]> wrote: > eliminate the annoyance that is friend > dependencies (or at least provide ways to externally override)
https://github.com/jglick/yenta lets you override this. YMMV A long time ago I wrote up http://wiki.netbeans.org/NbmPackageStability to discuss problems with the versioning scheme in NB and propose a different system. At this point I would say that the proposed change is unnecessarily complex, and that better development practices would avoid most problems: · Use simple specification version dependencies, and mark all packages public which you would expect any other modules to refer to. · If an API is intended to be used only under certain circumstances, document that. · If you suspect an API might be wrong and might be broken in the future, document that in boldface. · If you have no choice but to make a breaking change, communicate it properly. Look proactively for clients which might be broken, and offer fixes for them in advance. · Treat version numbers as an opaque ordering—just increasing numbers. Do not pretend that different components of a version number mean anything about compatibility. Without data, you do not know this. · Run integration tests aggressively. · Use Dependabot to keep dependencies up to date, so incompatibilities do not catch you by surprise. · If as a client you do find an incompatibility, communicate that to the developer of the API. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
