[
https://issues.apache.org/jira/browse/SOLR-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095452#comment-18095452
]
ASF subversion and git services commented on SOLR-18302:
--------------------------------------------------------
Commit af89e0379f3e499a46a88b7c7483aa5c0ea6e474 in solr's branch
refs/heads/main from Serhiy Bzhezytskyy
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=af89e0379f3 ]
SOLR-18302: dependency-analysis (DAGP) — reporting + build hygiene (#4612)
Adds the Dependency Analysis Gradle Plugin (com.autonomousapps
build-health) as an opt-in `analyzeDependencies` task — it reports
advice, doesn't fail the build, since api-vs-implementation calls need
human judgement rather than blanket enforcement.
- Remove redundant project() declarations that solr-core already
provides via api (24 across 17 modules) — cutterslade-era
"state the obvious" leftovers.
- Force kotlin-metadata-jvm to Solr's Kotlin so DAGP can analyze
:solr:ui (autonomousapps/dependency-analysis-gradle-plugin#1661;
temporary).
- Ensure lockfile doesn't have spotless or DAGP related special configurations.
Co-authored-by: David Smiley <[email protected]>
> Adopt the dependency-analysis (build-health) Gradle plugin
> ----------------------------------------------------------
>
> Key: SOLR-18302
> URL: https://issues.apache.org/jira/browse/SOLR-18302
> Project: Solr
> Issue Type: Task
> Components: Build
> Reporter: Serhiy Bzhezytskyy
> Priority: Major
> Labels: pull-request-available
> Time Spent: 7h
> Remaining Estimate: 0h
>
> Follow-up to SOLR-18289 (Gradle 9 upgrade), which removed the old cutterslade
> dependency-analysis plugin and deferred re-introducing dependency analysis.
> This adds the com.autonomousapps.build-health ("DAGP") plugin, wired into
> `check` in report-not-fail mode (severity: warn) so it reports advice without
> breaking the build. It also applies the safe, mechanical subset of that
> advice: removing genuinely-unused dependencies and correcting a few
> test-scope declarations.
> The plugin also suggests promoting many dependencies from `implementation` to
> `api`. Those are viral/transitive and need case-by-case human judgement, so
> they are handled separately (as draft PRs for discussion) rather than applied
> wholesale here.
> Discussed on the dev@ list as a follow-up to the Gradle 9 work.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
