Hi We simply can not maintain too many similar libraries ... it will be better to put power to one.
plexus-utils also looks like a swiss army knife for me: cli, dag(???), interpolation, introspection, io, reflection, xml .... some of tham also is in shared-utils Today many features can be replaced by JDK >= 1.8 We can also we existing library like commons-io, and so on - even when we need make a fix in it - will be better than maintain next own wt., 28 mar 2023 o 20:18 Konrad Windszus <[email protected]> napisał(a): > Hi, > The initial goal of maven-shared-utils from > https://maven.apache.org/shared/maven-shared-utils/ was never reached as > plexus-utils was never decommissioned but rather received most attention in > the past. > Lots of new bugfixes only ended up in plexus-utils and were never > backported to maven-shared-utils. > Given that I would propose to officially deprecated maven-shared-utils and > instead recommend using either plexus-utils or Apache Commons libraries > (IO, Lang3, …). > Afterwards we should get rid of all dependencies towards it from all Maven > Plugins and Core. > > Currently we have the unfortunate situation that the code is duplicated > without a clear way forward. > The only feature which is not found in plexus-utils is > https://maven.apache.org/shared/maven-shared-utils/apidocs/org/apache/maven/shared/utils/logging/package-summary.html > but that has been added to Maven 4 API meanwhile and potentially can be > easily added to plexus utils. > > WDYT? > > Konrad > > -- Sławomir Jaranowski
