Maven Dashboard Pro
The definitive Maven management experience for VS Code — an Eclipse- and IntelliJ-inspired dashboard that brings project explorer, dependency analysis, profile switching, and real-time build monitoring directly into your editor. Built for Java backend developers working with Spring Boot, Tomcat, microservices, and enterprise multi-module Maven workspaces.
Why Maven Dashboard Pro
VS Code's Java tooling has never had a first-class Maven experience comparable to Eclipse's "Maven Projects" view or IntelliJ's "Maven" tool window. Maven Dashboard Pro closes that gap: detect every Maven module in your workspace, run any goal without touching a terminal, and audit your dependency graph for conflicts, outdated versions, and known vulnerabilities — all from a dedicated Activity Bar sidebar.
Features
🗂️ Project Explorer
- Automatic detection of Maven projects, parent/child relationships, and multi-module reactors
- Structured tree: Modules → Lifecycle → Dependencies → Plugins → Repositories → Profiles → Metadata
- Build status badges, Spring Boot detection, and rich hover tooltips on every node
- Click any lifecycle phase (
validate → deploy) to run it instantly
📦 Dependency Explorer
- All dependencies across every module, grouped by scope (
compile, test, provided, runtime)
- Conflict detection — same
groupId:artifactId resolved at different versions
- Outdated-version checks against Maven Central
- Known-vulnerability flags sourced from OSV.dev
- One-click "Upgrade to Latest Version" that edits your
pom.xml directly
- Filter lens: All / Conflicts only / Outdated only / Vulnerable only
⚙️ Profile Explorer
- View every declared
<profile> across the workspace, with activation conditions
- Activate / deactivate profiles per project — applied automatically to subsequent goal runs (
-P)
📊 Build Monitor
- Real-time view of active executions, elapsed time, and exit status
- Full build history (persisted across editor restarts) with one-click stop for running builds
- Theme-aware webview that matches your editor's light/dark/high-contrast theme
🕸️ Dependency Graph
- Interactive, pannable/zoomable radial graph of a project's dependency tree
- Color-coded by scope, with conflict/outdated/vulnerable nodes highlighted
▶️ One-click goal execution
Run any of these directly from the toolbar or right-click menu — no terminal required:
clean · validate · compile · test · package · verify · install · deploy · dependency:tree · dependency:analyze · spring-boot:run · or any custom goal string.
🔍 Diagnostics & health checks
One command (Maven: Run Project Diagnostics) surfaces:
- Missing source encoding / Java version configuration
- SNAPSHOT dependencies in non-snapshot builds
- Dependency version conflicts
- Outdated plugin versions
- Recommendations for large multi-module reactors (parallel build flags)
🛠️ Maven environment management
- Auto-detects
mvn via MAVEN_HOME, M2_HOME, or PATH — or set a custom executable path
settings.xml validation (existence, well-formedness, duplicate server IDs)- Local repository cache inspection and one-click clearing
- Effective POM viewer (
mvn help:effective-pom) for full parent/profile resolution
🔄 Live workspace sync
- Watches every
pom.xml in the workspace and auto-refreshes the dashboard on change
- Status bar shows the active project and current build state at a glance
- Activity Bar badge surfaces running/failed build counts without opening the sidebar
Getting started
- Install Maven Dashboard Pro and open a workspace containing one or more
pom.xml files.
- Click the Maven icon in the Activity Bar.
- The Projects view scans automatically; if Maven isn't detected, you'll be prompted to select your
mvn executable.
- Right-click any project for the full goal/build menu, or use the toolbar buttons.
Configuration
| Setting |
Description |
Default |
mavenDashboardPro.maven.executablePath |
Path to a custom mvn/mvn.cmd |
(auto-detect) |
mavenDashboardPro.maven.settingsXmlPath |
Path to a custom settings.xml |
~/.m2/settings.xml |
mavenDashboardPro.maven.localRepositoryPath |
Path to the local repository |
~/.m2/repository |
mavenDashboardPro.maven.defaultOptions |
Extra args appended to every run |
(none) |
mavenDashboardPro.maven.offline |
Run Maven with -o |
false |
mavenDashboardPro.workspace.excludeGlobs |
Globs excluded when scanning for pom.xml |
target/, node_modules/, .git/ |
mavenDashboardPro.workspace.autoRefreshOnPomChange |
Auto-refresh on pom.xml edits |
true |
mavenDashboardPro.dependencies.checkForUpdates |
Query Maven Central for newer versions |
true |
mavenDashboardPro.dependencies.vulnerabilityScanning |
Query OSV.dev for known CVEs |
true |
mavenDashboardPro.build.terminalMode |
task | integratedTerminal | outputChannel |
task |
mavenDashboardPro.build.historySize |
Max build history entries retained |
50 |
mavenDashboardPro.statusBar.enabled |
Show status bar Maven indicator |
true |
mavenDashboardPro.logging.level |
Output channel verbosity |
info |
Privacy & network use
Dependency update checks call search.maven.org; vulnerability scanning calls api.osv.dev. Both are best-effort, opt-out via the settings above, and degrade silently if unreachable (e.g. offline or behind a corporate proxy) — no other network calls are made.
Requirements
- VS Code 1.85 or newer
- Apache Maven 3.6+ installed and reachable (or configured via settings)
- Java (for actually building/running your projects — Maven Dashboard Pro does not bundle a JDK)
Contributing & feedback
Found a bug or have a feature request? Use the 👎 feedback button in chat-based environments, or open an issue in the repository. Logs are available via Maven: Show Maven Output.
License
MIT — see LICENSE.
