On 21 April 2017 at 13:59, sebb <seb...@gmail.com> wrote: > What happens when there is a API break which necessitates a package name > change? > I assume that the module name will also need to change to the new > super-package. > e.g. > > Commons-Lang4 > -> super-package org.apache.commons.lang4 > -> module org.apache.commons.lang4
Yes, thats right. > AFAICT Commons generally has obvious and unique super-packages for > each component. > This should make it easier than for larger projects with lots of jars > and potentially overlapping package names. > > However even Commons has some code that uses a different package structure. > e.g. NET uses examples as the super-package. > This includes working examples that are included in the release. > I guess that will have to change (which is probably a good idea anyway). Yes, as it stands, [net] would be a bad modular citizen, because it exposes the "examples" package, and thus prevents any other module from using that package. Just move it to org.apache.commons.net.examples. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
