-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] RHDA is attempting to put a slash at the beginning of the path to my POM, causing the help:effective-pom mvn command to fail #681
[BUG] RHDA is attempting to put a slash at the beginning of the path to my POM, causing the help:effective-pom mvn command to fail #681
Comments
I think I have a problem like yours: |
Same for me:
|
me too, so it seems that only the slash after the -f option is the issue. |
same thing happening here, I've downgraded the extension for now and it is working, but the current version is bugged |
Which version did you downgrade to? I'd love to know so I can make the switch. I'm working on moving my projects to Gradle right now, but until then I would love to have this plugin working for my Maven stuff. |
I decided to test to see if downgrading to 0.9.1 fixes the problem, but unfortunately, it's a no-go. I got some invalid JSON response and requests to the https://rhdacloud.com/api/v4/analysis failures. EDIT: It seems downgrading to any versions are all no-goes. I get a lot of invalid JSON response bodies for each downgrade: 0.9.0, 0.7.3, etc.
|
Same here: I can´t generate effective pom with extension v0.9.2 because the slash at the beginning of the path. If I downgrade to v0.9.0 RHDA don´t work with error "request to https://rhda.rhcloud.com/api/v4/analysis failed, reason: connect ETIMEDOUT 18.119.151.206:443" |
Thank you @natereprogle and all for reaching out regarding this issue. |
Thank you! That's awesome 👏🏼 |
Vielen Dank für Ihre harte Arbeit! |
I too have suffered from this problem for a while now on |
2 versions (v0.9.3 and v0.9.4) of the RHDA extension have been published after the fix fabric8-analytics/fabric8-analytics-lsp-server#244, but neither of them includes it. When do you expect to release a version of RHDA that includes it? Is it possible to download a packaged version of RHDA LSP Server to manually replace it locally? Thanks in advance |
Same issue. I don't want to disable the extension just to get rid of this error, but it would be great to have a fix |
Downgraded to 0.9.1 and it seems to be working without the issue. |
@elTorres the fix will be included in the next release, version 0.9.5. You can expect it very soon. We don't offer pre-packaged versions for manual replacement, but once 0.9.5 is out, you'll be able to update your RHDA extension. Thanks for your patience. |
Downgrading RHDA fixed my problem too, thank you. |
v1.30.0 appears again. |
@aphage It is likely because 0.9.5 isn't out publicly. I'm just guessing. |
I encountered the same problem on v0.9.4. When will the fix be published? |
Any news @IlonaShishov ? |
We are still working on the fix for your issue and apologize for the delays. We will notify you as soon as it is available. |
Hello, This issue has been resolved in the latest release, version 0.9.5. We appreciate your help in improving the project. If you have any further issues or suggestions, please feel free to reach out. Best regards. |
Describe the bug
Every time I focus on my pom.xml in my project, I get the following error:
Running this command manually also gives the same error, but removing the
/
from in front ofv:/
in the -f argument generates the effective-pom as expected. I have attempted to look through different configuration settings, update Maven to the latest version, etc. with no results.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The effective-pom.xml is generated, and I am able to analyze dependencies as normal
Screenshots
I am able to control click the file it says doesn't exist and navigate to it within VSCode without issue. This is not a symlink or shortcut, it is the actual file itself.
Logs
The only logs I see are in the output window of VSCode, which just state the error I am receiving above.
log.log
VSCode(please complete the following information):
Additional context
The -Doutput flag doesn't need to change, strangely enough. It uses
\
instead of/
, but the file is generated fine. However, even if I change the -f argument to use\
instead of/
, it still fails when run manually, with the same result.The text was updated successfully, but these errors were encountered: