On 5 June 2016 at 18:51, Thomas Vandahl <t...@apache.org> wrote: > On 03.06.16 10:38, sebb wrote: >> On 2 June 2016 at 21:42, Benedikt Ritter <brit...@apache.org> wrote: >>> - we must not break BC in a release that could collide with an earlier >>> version. In other words, when we break BC, we have to change package and >>> maven coordinates. >> >> +1, with the proviso that we must not break BC in the *public* API. >> Unfortunately it is not always clear what is public. >> > > All commons components are released with OSGi bundle metadata, where the > packages for a public API can be stated. If this information is > maintained correctly, everyone should be able to tell public from > private API changes.
The problem is determining what is supposed to be public, not documenting it. Though I would question whether non-OSGi users would think to look at the metadata. > Bye, Thomas. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
