Fix Windows process launch failures with long executable paths#24
Draft
Fix Windows process launch failures with long executable paths#24
Conversation
Add shortenWindowsCommandLine() to shorten all command line arguments that exceed Windows MAX_PATH limit, not just the working directory. This fixes issues where Eclipse is unable to launch processes with long executable paths on Windows. The fix uses Windows GetShortPathName API via Win32Handler to convert long paths to their 8.3 short form before passing them to ProcessBuilder or Runtime.exec(). Co-authored-by: laeubi <1331477+laeubi@users.noreply.github.com>
Add testProcessLaunchWithLongExecutablePath() to verify that processes can be launched when the executable path exceeds Windows MAX_PATH limit. The test creates a directory with a very long path, copies java.exe to it, and verifies the executable can be launched successfully. Co-authored-by: laeubi <1331477+laeubi@users.noreply.github.com>
- Fix spelling: 'relativly' -> 'relatively' - Add constants for magic numbers (WINDOWS_MAX_PATH, LONG_PATH_LENGTH_TARGET) - Use constants instead of hardcoded values for better maintainability Co-authored-by: laeubi <1331477+laeubi@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix native code handling of long path for Windows API
Fix Windows process launch failures with long executable paths
Oct 30, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Eclipse fails to launch processes when executable paths exceed Windows' 260-character MAX_PATH limit. The existing code only shortened working directories, not the executable path itself.
Changes
Core Fix (DebugPlugin.java)
shortenWindowsCommandLine()to handle long paths in all command-line argumentsGetShortPathNameAPI via existingWin32Handlerto convert to 8.3 formatProcessBuilder,Runtime.exec(), andExecFactorydelegationTest Coverage (LaunchTests.java)
testProcessLaunchWithLongExecutablePath()Example
Before this fix, launching a process would fail:
After:
Technical Note
Cannot use
\\?\long path prefix as Java's process creation APIs reject it (JDK-8315405). Short path conversion is the most reliable workaround.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
repo.eclipse.orgIf you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.