apache / apache/maven-jdeps-plugin

[MJDEPS-14] Provide a JDEPS report for inclusion within Maven site

Open
#47 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
18
Forks
18
Avg merge
9h 12m
Merged PRs (30d)
5

Description

**[Lennart Jörelid](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=lennartj)** opened **[MJDEPS-14](https://issues.apache.org/jira/browse/MJDEPS-14?redirect=false)** and commented

While the JDEPs is good to run as a control plugin, it is also really a good structural addition to JDK8 and JDK9 build reactors to harvest information about dependencies between projects/modules. 

The jdeps tool can already emit DOT files - so we can compile those into graphics shown in a report on the maven site. The majority of the work is - hence - already done. However, this requires that graphviz is installed on the computer (similar to the case when generating PlantUML diagrams). Graphviz (or even its constituent application, DOT) ought to be treated like just-another-Toolchain within the plugin.

---

1 votes, 2 watchers

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the plugin's existing jdeps/DOT generation and Maven site-report entry points; the issue names no files or tests. Review how PlantUML handles Graphviz-like external tools, then define the report and toolchain integration. Done means dependency data is rendered as graphics in the Maven site when Graphviz is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.