Hi All, There are some many ways this can create jar hell now and in the future that I would not want to risk it. Binary compatibility is something we should strive for IMO. If this change is _that_ important, then it's 2.0 time. Otherwise, don't break application stacks. Especially since Commons components tend to live at the bottom of such stacks. I see plenty of stacks out there for example, that include _both_ [lang] and [lang3], and that is _fine_.
Gary On Mon, Jan 15, 2018 at 5:13 AM, Gilles <gil...@harfang.homelinux.org> wrote: > Hi. > > Please have a look at this issue on JIRA: > https://issues.apache.org/jira/browse/RNG-46 > and confirm that a release won't be blocked by the > current "clirr" report. > > Thanks, > Gilles > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
