I've been working on this, here and there as time permits, as have
others. I think there are a number of issues already filed. I've
deprecated a lot of individual methods. Indeed I have an open PR to
deprecate a couple more that can be merged as soon as someone
approves:

https://github.com/apache/maven-shared-utils/pull/136

Some pieces are easier than others. The IO and StringUtils can pretty
much all go at this point. A lot of that can be replaced by pure JDK
methods in any Java 8+ VM. The CLI, introspection, and logging
libraries are perhaps trickier.

@timtebeek has recently started using some really interesting
automated tooling to fix some of this in bulk without a lot of the
manual grunt work normally required. E.g.
https://github.com/apache/maven-doxia/pull/156/files

Send more PRs my way. :-)


On Tue, Mar 28, 2023 at 2:18 PM Konrad Windszus <[email protected]> wrote:
>
> 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
>


-- 
Elliotte Rusty Harold
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to