[jira] [Updated] (GSOC-336) [GSoC 2027] Build-Aware Dependency Tracking for Maven 4

["Romain Manni-Bucau (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GSOC-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau updated GSOC-336:
------------------------------------
    Labels: gsoc gsoc2027 maven mentor  (was: gsoc gsoc2026 maven mentor)

> [GSoC 2027] Build-Aware Dependency Tracking for Maven 4
> -------------------------------------------------------
>
>                 Key: GSOC-336
>                 URL: https://issues.apache.org/jira/browse/GSOC-336
>             Project: Comdev GSOC
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>            Priority: Major
>              Labels: gsoc, gsoc2027, maven, mentor
>
> *Background:*
> Maven users can trace where a dependency comes from in the
> resolution graph, but not why it ends up (or doesn't) in the
> final packaged artifact. Packaging plugins (WAR, assembly, shade)
> make their own include/exclude decisions after resolution, and
> there's currently no way to trace an artifact from resolution
> through to its final location in the archive.
> *Goals:*
>  - Port existing file-based dependency tracking to an in-memory,
>   session-scoped store (Maven 4)
>  - Design a new SPI allowing packaging plugins to report artifact
>   usage decisions
>  - Implement the SPI in maven-war-plugin as a proof of concept
>  - Provide a report goal (dependency-tracker:report) producing
>   text or JSON output
> Expected outcome: a single command that explains why a specific
> JAR is (or isn't) present in a project's final packaged output.
> *Mentor:* Romain Manni-Bucau
> *Expected Assignee:* B V Hitesh Sai



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: gsoc-unsubscribe@community.apache.org
For additional commands, e-mail: gsoc-help@community.apache.org