Maven dependency analysis and conflict detection tool, support dependency tree display, dependency path display, dependency conflict detection, dependency exclusion, etc.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
A professional Maven dependency analysis tool, designed to fill a gap in the VSCode ecosystem and significantly boost your development efficiency.
In a VSCode environment that lacks a native and powerful Maven dependency management tool, Maven Helper provides an intuitive dependency tree and professional conflict detection to help you easily manage complex project dependencies.
Quick Start
1. Installation
Search for "Maven Helper" in the VSCode Extension Marketplace and click Install.
2. Prerequisites & Configuration (Important)
Correctly configuring the environment is key to ensuring the extension works properly and is the most common source of issues.
Java Environment: Ensure the JAVA_HOME environment variable is set correctly and points to your JDK directory.
Maven for Java Extension: It is highly recommended to install this official extension. Maven Helper will attempt to retrieve Maven configurations from it.
Manual Configuration (if needed): If the extension cannot find your Maven installation automatically, or if you need to use a specific configuration, add the following to your VSCode settings.json:
"maven.executable.path": "/path/to/your/mvn", // must end mvn
"maven.settingsFile": "/path/to/your/settings.xml" // must end .xml
3. Usage
Open a Maven project containing a pom.xml file.
Find and click the "Maven Helper" icon in the left Activity Bar.
The panel will display your projects; click on a project to start the analysis.
4. Frequently Asked Questions (FAQ)
Q: How can I troubleshoot a Maven dependency analysis failure?
A: Enable maven-helper.log.debug in VSCode settings, then run the dependency analysis again. Click “Show Logs” in the Maven Helper panel, or select “Maven Helper” in the Output panel, to view the Maven command and working directory, arguments, JAVA_HOME, PATH, and the complete Maven command.
Find the [DEBUG] Maven 完整命令: log entry, copy the command, and run it directly in the working directory shown in the log to see Maven's complete error output. Check the Maven executable, JDK, settings.xml, private repository permissions, and depgraph plugin downloads first.
Configuration Options
maven-helper.dependency.showGroupId: (boolean, defaults to false)
Controls whether to show the GroupID in the dependency tree.
maven-helper.log.debug: (boolean, defaults to false)
Controls whether to print detailed debug logs in the "Output" panel.
maven-helper.maven.useNativeDependencyTree: (boolean, defaults to false)
Controls the dependency analysis execution mode.
false (default): Uses the faster depgraph plugin for analysis.
true: Switches to the native dependency:tree -Dverbose command. Try this option if the depgraph mode encounters issues.
