Skip to content

Clean up declared dependencies #13749

Closed
Closed

Description

@slachiewicz

mvn dependency:analyze across the Maven repositories reports dependencies that are declared but unused, declared in the wrong scope or in a parent that does not need them, and third-party libraries the code uses but only gets transitively. Every finding below was checked against the sources, applied in a separate pull request per repository, and kept only if the full test suite still passed; the analysis then no longer reports it.

Not changed on purpose: used-but-undeclared Maven API, Sisu/Guice/javax.inject, test-framework and SLF4J artifacts (declaring Maven core artifacts follows separately), and anything that only a build with GraalVM, or an external tool, could verify.

Pull requests:

Declaring the artifacts the code uses directly:

Activity

  1. gnodet commented on Oct 29, 2026

    @gnodet
    Contributor

    Note that dependency:analyze has some flaws in its implementation. I would encourage to use pilot:dependencies instead.

    https://github.com/maveniverse/pilot

  2. slawekjaranowski commented on Oct 30, 2026

    @slawekjaranowski
    Member

    5. Note that dependency:analyze has some flaws in its implementation. I would encourage to use pilot:dependencies instead.
    https://github.com/maveniverse/pilot

    I would like to improve dependency:analyze also 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions