Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Maven HelperNew to Visual Studio Code? Get it now.
Maven Helper

Maven Helper

hendiaome

|
332 installs
| (1) | Free
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.
Copied to clipboard
More Info

Maven Helper for VSCode

专业的 Maven 依赖分析工具,旨在填补 VSCode 生态中的空白,大幅提升您的开发效率。

在缺少原生且强大 Maven 依赖管理工具的 VSCode 环境中,Maven Helper 提供了直观的依赖树和专业的冲突检测功能,帮助您轻松管理复杂的项目依赖。

功能截图

Free vs. Pro

Maven Helper 提供免费的基础版和功能更强大的 Pro 订阅版。您的订阅是对本项目持续发展的最大支持!

功能 (Feature) 基础版 (Free) Pro 版 (Subscription)
可视化依赖树 ✅ ✅
依赖引用路径分析 ✅ ✅
版本冲突高亮 ✅ ✅
依赖快速筛选 ✅ ✅
GroupID 显示切换 ✅ ✅
跳转到依赖定义 (pom.xml) ❌ ✅
快速排除冲突依赖 ❌ ✅
未来所有高级功能 ❌ ✅

❤️ 成为 Pro 会解锁核心效率功能!


快速开始

1. 安装

  • 在 VSCode 扩展市场中搜索 "Maven Helper" 并点击 安装。

2. 环境依赖与配置 (重要)

正确配置环境是保证插件正常运行的关键,也是最容易出错的环节。

  • Java 环境: 请确保 JAVA_HOME 环境变量已正确设置并指向您的 JDK 目录。
  • Maven for Java 扩展: 强烈建议安装此官方扩展。Maven Helper 会尝试从此扩展中获取 Maven 的配置。
  • 手动配置 (如果需要): 如果插件无法自动找到您的 Maven,或者您需要使用特定的配置,请在 VSCode 的 settings.json 中添加以下配置:
    "maven.executable.path": "/path/to/your/mvn", // must end mvn
    "maven.settingsFile": "/path/to/your/settings.xml" // must end .xml
    

3. 使用方法

  1. 打开包含 pom.xml 的 Maven 项目。
  2. 在左侧活动栏中找到并点击 "Maven Helper" 图标。
  3. 面板将显示您的项目列表,点击项目即可开始分析。

4. 常见问题 (FAQ)

  • Q: 升级 Pro 时提示端口被占用?
  • A: 这是因为用于认证的端口(默认为 7891)已被其他程序(例如代理工具 Clash)占用。请关闭相应程序,或通过任务管理器/命令行 kill 掉对应的进程后,重试认证即可。

配置选项

  • maven-helper.dependency.showGroupId: (boolean, 默认为 false)
    控制依赖树中是否显示 GroupID。

  • maven-helper.log.debug: (boolean, 默认为 false)
    控制是否在 "输出" 面板中打印详细的调试日志。

  • maven-helper.maven.useNativeDependencyTree: (boolean, 默认为 false)
    控制 Maven 依赖分析的运行模式。

    • false (默认): 使用速度更快的 depgraph 插件进行依赖分析。
    • true: 切换到原生 dependency:tree -Dverbose 命令。如果 depgraph 模式遇到问题,可尝试此选项。

支持与反馈

  • 问题报告: GitHub Issues
  • 项目仓库: GitHub Repository


Maven Helper for VSCode (English)

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.

Free vs. Pro

Maven Helper offers a free version with essential features and a Pro subscription version with enhanced capabilities. Your subscription is the greatest support for the continuous development of this project!

Feature Free Version Pro Version (Subscription)
Visual Dependency Tree ✅ ✅
Dependency Reference Path Analysis ✅ ✅
Version Conflict Highlighting ✅ ✅
Quick Dependency Filtering ✅ ✅
Toggle GroupID Display ✅ ✅
Jump to Definition in pom.xml ❌ ✅
Quickly Exclude Conflicting Dependencies ❌ ✅
All Future Advanced Features ❌ ✅

❤️ Become a Pro to Unlock Core Productivity Features!


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

  1. Open a Maven project containing a pom.xml file.
  2. Find and click the "Maven Helper" icon in the left Activity Bar.
  3. The panel will display your projects; click on a project to start the analysis.

4. Frequently Asked Questions (FAQ)

  • Q: Port is in use when upgrading to Pro?
  • A: This happens because the port used for authentication (default 7891) is occupied by another application (e.g., a proxy tool like Clash). Please close the conflicting application, or kill the corresponding process via Task Manager / command line, and then try the authentication again.

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.

Support and Feedback

  • Issue Reports: GitHub Issues
  • Project Repository: GitHub Repository
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft