Feature Request: Add jdt_maven_update_project tool #4

New issue

Closed

opened 2026-02-05 10:21:20 +00:00 by automation · 0 comments

automation commented

2026-02-05 10:21:20 +00:00

Collaborator

Problem

When Maven POM files are modified (e.g., changing groupId, adding dependencies), the jdt_refresh_project tool only refreshes files from the filesystem but does not update Maven dependencies in Eclipse.

This results in "build path errors" that can only be resolved by manually running "Maven > Update Project" in Eclipse.

Proposed Solution

Add a new tool jdt_maven_update_project (or similar) that triggers the M2E "Update Project" functionality:

// Equivalent to: Right-click project → Maven → Update Project
IProjectConfigurationManager configManager = MavenPlugin.getProjectConfigurationManager();
configManager.updateProjectConfiguration(project, monitor);

Use Case

When using JDT MCP for refactoring that involves:

Moving types to new packages with different groupId
Adding/removing Maven dependencies
Changing artifact coordinates

The workflow would be:

Edit pom.xml files
Call jdt_maven_update_project
Call jdt_refresh_project
Continue with compilation error checks

Current Workaround

Users must manually update Maven projects in Eclipse IDE or run mvn install to work around this limitation.

## Problem When Maven POM files are modified (e.g., changing groupId, adding dependencies), the `jdt_refresh_project` tool only refreshes files from the filesystem but does not update Maven dependencies in Eclipse. This results in "build path errors" that can only be resolved by manually running "Maven > Update Project" in Eclipse. ## Proposed Solution Add a new tool `jdt_maven_update_project` (or similar) that triggers the M2E "Update Project" functionality: ```java // Equivalent to: Right-click project → Maven → Update Project IProjectConfigurationManager configManager = MavenPlugin.getProjectConfigurationManager(); configManager.updateProjectConfiguration(project, monitor); ``` ## Use Case When using JDT MCP for refactoring that involves: - Moving types to new packages with different groupId - Adding/removing Maven dependencies - Changing artifact coordinates The workflow would be: 1. Edit pom.xml files 2. Call `jdt_maven_update_project` 3. Call `jdt_refresh_project` 4. Continue with compilation error checks ## Current Workaround Users must manually update Maven projects in Eclipse IDE or run `mvn install` to work around this limitation.