[
https://issues.apache.org/jira/browse/MSHARED-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17753329#comment-17753329
]
ASF GitHub Bot commented on MSHARED-1289:
-----------------------------------------
elharo commented on PR #165:
URL:
https://github.com/apache/maven-shared-utils/pull/165#issuecomment-1675272349
Still a hard no on this one. This needs to be dealt with one piece at a
time, not as a single PR that deprecates things that are in use and that we
don't have replacements for. Even more importantly, we need to eliminate
plexus-utils, not reintroduce it. The foggy ownership and licensing story make
it infeasible for Apache projects.
> Deprecate maven-shared-utils
> ----------------------------
>
> Key: MSHARED-1289
> URL: https://issues.apache.org/jira/browse/MSHARED-1289
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-shared-utils
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> As discussed in
> https://lists.apache.org/thread/9wkmo1cfq7hx6qwo2xp070rkdz1w5myp this library
> never became successor of plexus-utils and therefore is less maintained.
> Instead of maintaining two libraries we should deprecated Maven Shared Utils
> and recommend using plain JDK API where possible or fall back to either
> plexus-utils or other well known third party libraries.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
