Repository navigation
Failed to resolve classpath: Main class 'Main' isn't unique in the workspace #21
Description
Open a java folder, see the screenshot below.
And click F5 to launch, it popup a message box saying that Failed to resolve classpath: Main class 'Main' isn't unique in the workspace, please pass in specified projectname..
Apparently it's not a normal eclipse/maven/gradle project, but just a simple java file. In such case, these java files will be linked to a fake project. It seems the main class isn't unique in the fake project. But in such case, user doesn't know how to specify project name. We need figure out how to handle such kind of case.
Activity
akaroml commentedon Sep 15, 2017
This is the feature to support debugging single file. Assign to Xuan Zhou (@ansyral).
ansyral commentedon Oct 12, 2017
couldn't repro it yet because currently our debugger doesn't support single file debug without configuration. I'll test it after we update our debugger with new debug protocol and support single file debug following microsoft/vscode#33791 (comment)
ansyral commentedon Oct 13, 2017
could repro for projects that has main class whose package is default
deed02392 commentedon Mar 22, 2018
I had this error.
To repro: install the Java Extension Pack. Create a new maven generate archetype - select folder - choose maven-archetype-quickstart.
Provide groupid etc in the PowerShell console.
It generates the package and class
App.Try to debug (Launch) the App class - not unique error.
I worked around this by renaming
Appfile and class (obviously) toApplol.andxu commentedon Mar 23, 2018
The bug for 'Main' isn't unique in the workspace still happens, reopen it
andxu commentedon Jun 19, 2018
I will collect this kind of error in telemetry later.
andxu commentedon Aug 31, 2018
DUP as microsoft/vscode-java-debug#331