In my view no blocker at all. Just in case another 2.5.x would have been in the pipeline it would have been sensible to update those too.
However, no matter how quick we try to follow the update process of secondary libraries in the official struts distro, we will always be out of date in a couple of days, since this is a dynamic situation. So we may leave this very well up to individual responsibility to do so. Best Markus Am 19.08.20 um 08:52 schrieb Lukasz Lenart: > wt., 18 sie 2020 o 10:27 i...@flyingfischer.ch <i...@flyingfischer.ch> > napisał(a): >> PS: maybe to consider for an upcoming release: there are some newer >> version of used librarires which do work fine in Struts2, as >> >> commons-collections4-4.4 >> commons-io-2.7 >> commons-lang3-3.11 (would need to check, if commons-text has been split >> off, which needs failureaccess, if I am not mistaken) >> log4j-2.13.3 > Do you consider this as a blocker? I rather do not plan another 2.5.x > version, I would like to focus on 2.6 now. > > > Regards --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
