[
https://issues.apache.org/jira/browse/MNG-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707546#comment-17707546
]
Tim te Beek commented on MNG-6825:
----------------------------------
Thanks for the continued offer to review [~elharo] ! I've passed on your note
about the "co-authored by Moderne" to see how we can best alleviate those
concerns; we specifically setup
[https://public.moderne.io|https://public.moderne.io/] for OSS projects to use
the platform. The co-authored is merely a way to attribute those changes such
that it's clear automation was involved. It should not be a hindrance to see
changes adopted, and have asked if this can be confirmed here, or by signing
the CCLA.
As for [~sjaranowski] : I understand your concerns about the release notes for
individual projects, but want to make it clear exactly what you're asking, and
how that might affect the effort involved here. At present the code changes are
automated through the platform UI, but that automation does not extend to cover
Jira ticket creation. Looking at Jira there are some 72 projects defined, with
a unknown mapping to the 89 repositories available in the platform; here's the
full list of projects I see in Jira right now, to give sense of scale:
ARCHETYPE, DOXIA, DOXIASITETOOLS, DOXIATOOLS, JXR, MACR, MANT, MANTRUN,
MANTTASKS, MARCHETYPES, MARTIFACT, MASFRES, MASSEMBLY, MBUILDCACHE, MCHANGELOG,
MCHANGES, MCHECKSTYLE, MCLEAN, MCOMPILER, MDEP, MDEPLOY, MDOAP, MDOCCK, MEAR,
MECLIPSE, MEJB, MENFORCER, MGPG, MINDEXER, MINSTALL, MINVOKER, MJAR,
MJARSIGNER, MJAVADOC, MJDEPRSCAN, MJDEPS, MJLINK, MJMOD, MLINKCHECK, MMETRIC,
MNG, MNGSITE, MPATCH, MPDF, MPH, MPIR, MPLUGIN, MPLUGINTESTING, MPMD, MPOM,
MRAR, MRELEASE, MREPOSITORY, MRESOLVER, MRESOURCES, MRRESOURCES, MSCMPUB,
MSCRIPTING, MSHADE, MSHARED, MSITE, MSKINS, MSOURCES, MSTAGE, MTOMCAT,
MTOOLCHAINS, MVERIFIER, MWAR, MWRAPPER, SCM, SUREFIRE, WAGON
If you would like to see individual tickets per change per project we would
have to:
# define a mapping from repository to project, needed to attribute repository
code changes to Jira projects
# ditch the platform UI and switch to a GraphQL API client to detect
applicable code changes
# automated the creation of a ticket per project, likely linking back here for
a full description
# create the the code change PR per repository using the appropriate commit
message with ticket reference
# close the individual project tickets as completed when the PRs are merged
(but only on full transformations)
We'll likely have to do multiple rounds of 2-5 for additional changes, for the
initial migration of StringUtils to commons-lang3, and then later the
subsequent migration to JDK internals when language levels allow. This would
require a substantial time investment to setup that automation; which while
not impossible, would be harder to fit into my schedule as opposed to using the
platform UI. The upside would be that it'd be easier to apply more such changes
in the future while reflecting all such changes in the release notes.
Given that I'll be traveling for much of April through July for conferences I
fear the required API setup and integration with Jira will then only happen
after the summer, and any code changes would have to wait for that, unless
anyone else wants to step up to help out.
> Cleaning Up dependencies
> plexus-utils/maven-shared-utils/commons-lang3/commons-io
> ---------------------------------------------------------------------------------
>
> Key: MNG-6825
> URL: https://issues.apache.org/jira/browse/MNG-6825
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 3.6.3
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Priority: Minor
> Fix For: 4.0.x-candidate
>
>
> Experiment to see if we can get rid of commons-lang3 dependency.
> * Identified code duplication between:
> ** {{org.apache.commons.lang3.StringUtils}} from {{commons-lang3}} (501879
> Bytes commons-lang3-3.8.1.jar)
> ** {{org.codehaus.plexus.util.StringUtil}} from {{plexus-utils}} (261801
> Bytes plexus-utils-3.2.1.jar)
> ** {{org.apache.maven.shared.utils}} from {{maven-shared-utils}} (166562
> Bytes maven-shared-utils-3.2.1.jar)
> ** We should replace the self implemented with
> {{org.codehaus.plexus.util.StringUtil}}. or with {{maven-shared-utils}}
> * {{commons-io}} usage by {{maven-shared-utils}} (208700 Bytes
> commons-io-2.5.jar)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
