vscode-maven icon indicating copy to clipboard operation
vscode-maven copied to clipboard

Maven for Java extension not activated even workspace contains pom.xml file

Open doggy8088 opened this issue 2 years ago • 4 comments

Describe the bug

I can't see Maven for Java extension been activated after project been loaded.

To Reproduce Steps to reproduce the behavior:

  1. Clone my project

    git clone https://github.com/doggy8088/spring-boot-jpa-demo.git
    code spring-boot-jpa-demo
    
  2. I can't see MAVEN extension been activated. I do have a pom.xml in the workspace.

    image

Expected behavior

I expected the MAVEN extension will be loaded if my workspace contains a pom.xml file. I don't know it seems unstable.

https://github.com/microsoft/vscode-maven/blob/2a254ba103708298e8b31172eb89ae4663e72f78/package.json#L39

Environments (please complete the following information as much as possible):

  • OS: Windows 10
  • VS Code version: v1.71.2
  • Extension version v0.39.0

Screenshots

image

Additional context

I do have a workaround by execute F1 > Maven: Add a dependency command once.

If the MAVEN extension has been activated successfully, you can try run Developer: Reload Window command. The MAVEN extension will not be loaded again after vscode window reloaded.

doggy8088 avatar Oct 06 '22 17:10 doggy8088

It was not activated somehow. Check Log(Extension Host) for logs about extension activation.

Eskibear avatar Oct 11 '22 02:10 Eskibear

Check this out:

image

I think the problem could be here. I installed too many extensions in my VSCode.

https://github.com/microsoft/vscode/blob/3f2adbfe3e6d07c60bc4c61b4ff7bdcf1c451792/src/vs/workbench/services/extensions/common/workspaceContains.ts#L90-L93

Related issue: https://github.com/microsoft/vscode/issues/73656

doggy8088 avatar Oct 11 '22 07:10 doggy8088

I think it's an upstream issue. I opened a new issue there: https://github.com/microsoft/vscode/issues/163255

doggy8088 avatar Oct 11 '22 07:10 doggy8088

also see: https://github.com/microsoft/vscode-maven/issues/881

Eskibear avatar Oct 11 '22 09:10 Eskibear

This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.

github-actions[bot] avatar Dec 02 '22 00:12 github-actions[bot]

let's track it in #881

Eskibear avatar Dec 02 '22 02:12 Eskibear