[BUG] RHDA can not open pom.xml when it is not in default disk (Windows)

[fravelgue]

Describe the bug
RHDA can not open pom.xml when it is not located in default disk. For example, X:\
It shows this error:

ENOENT: no such file or directory, access 'C:\fravelgue\learn-spring\pom.xml'

To Reproduce
Steps to reproduce the behavior:

1. Open pom.xml that is in a different disk to C:\. In the screenshot: X:\fravelgue\learn-spring\pom.xml
2. See error

Expected behavior
The effective-pom.xml is generated, and I am able to analyze dependencies as normal.

Screenshots

Logs
n/a

VSCode(please complete the following information):

• OS: Windows: 11 23H2
• VSCode version: 1.91.1
• Dependency Analytics Version: 0.9.5

Additional context
It works when using context menu (right button): Red Hat Dependecy Analytics Report.

[johnsteele]

I tried reproducing this issue on my mac, and I get different error, not sure if related.
I'm also running the extension from source, that too could make a difference.
I'll keep investigating.

[johnsteele]

Here's an update:

I've tested the VSCode extension from source, also being tested/referenced is the fabric8-analytics/fabric8-analytics-lsp-server from source, and I'm now no longer getting the previous error on the same package.json file.

So, maybe there's something in master of this repo, or something in master of fabric8-analytics-lsp-server that didn't make its way in the release. I'll keep investigating.

[PhilipCattanach]

Hi @johnsteele
My understanding of this issue is that the VSCode extension is producing an error message when trying to deal with a pom.xml file that is stored on a different disk drive to the default drive.
Now that you have overcome the issue you described above, have you been able to recreate the original issue?

[johnsteele]

Hi @PhilipCattanach
Yes, I did test on pom.xml and I was not able to reproduce this issue.