I keep thinking that too, and ended up just using a custom versions rule to ignore it.
Other idea maybe change to GAV to; 1) org.apache.commons:commons-io 2) org.apache.commons:commons-io2 So starting to match the commons-lang3 approach. I find commons-lang3 is a really good pattern and is much easier, as it supports older and newer versions on the classpath at the same time without conflict. Allowed phased upgrades. And an upgrade to lang3 from lang is just a find/replace "org.apache.commons.lang." to "org.apache.commons.lang3." and ticket off the build process to check it worked. Hopefully they will keep the same style for lang4 and it will just be another find/replace upgrade when i choose. On Sun, 14 Jun 2020 at 11:40, Xeno Amess <xenoam...@gmail.com> wrote: > > every time my update tool chain thinks 20030203.000550 is a greater version > than 2.7 (actually it is, if see it in number). > So have we some way to delete it from maven central? (or rename it?) > The same problem happened in BeanUtils, version 20030211.134440 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
