On Thu, 3 Sep 2020 at 13:07, Gilles Sadowski <gillese...@gmail.com> wrote: > > Le jeu. 3 sept. 2020 à 13:55, sebb <seb...@gmail.com> a écrit : > > > > On Wed, 2 Sep 2020 at 20:54, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > On Wed, Sep 2, 2020, 15:50 Xeno Amess <xenoam...@gmail.com> wrote: > > > > > > > Why so hurry? > > > > > > > > > > I need to use new APIs now. Releases happen all the time, more releases > > > more often is better than big bang releases IMO, IOW RERO (Release Early, > > > Release Often). > > > > > > Is there any severe bug solved? > > > > > > > > > > See changes.xml, severity is relative to one's needs. > > > > > > > > > > And here goes another question. > > > > why is commons-io's group ID be commons-io but not com. apache. commons? > > > > > > > > > > Backward compatibility. We can change it if and when we break BC for 2.0. > > > > This is a bit old, but I think it still applies: > > > > https://cwiki.apache.org/confluence/display/COMMONS/MavenGroupIDChange > > Unfortunately, the crucial part (about whether a "relocation POM" would work) > is missing. > There wouldn't be any BC issue.
*If* they worked as we would like. It could be a false hope. Last time I checked, it looked like a relocation POM was only checked if the Maven build attempted to access that particular version. However, I think relocation POMs can only be applied to the most recent version. That is inherently fragile. Since we have no proof that relocation POMs work, it is not safe to assume they can fix the issue. > Gilles > > --------------------------------------------------------------------- > 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
