You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am able to run and generate reports through the maven plugin. However I can not get it to run with the vscode extension. I see "Error running command gzoltar.run: A system error occurred (ENOENT: no such file or directory, stat '/workarea/target/classes'). This is likely caused by the extension that contributes gzoltar.run." whenever I run Gzoltar.
The way my project is setup is:
mainfolder
- packageA
- packageB
For the maven api i had updated the pom.xml inside packageA and left everything else as is and that seemed to work. And the maven reports are created inside packageA/target
Alternatively, is there a way that I can use the maven reports to visualise inside vscode?
Environment (please complete the following information, if relevant):
OS: Windows (WSL)
Version 1.7.3 for maven
Additional comments
I feel it must be something to do with the remote wsl?
The text was updated successfully, but these errors were encountered:
Context
I am able to run and generate reports through the maven plugin. However I can not get it to run with the vscode extension. I see "Error running command gzoltar.run: A system error occurred (ENOENT: no such file or directory, stat '/workarea/target/classes'). This is likely caused by the extension that contributes gzoltar.run." whenever I run Gzoltar.
The way my project is setup is:
mainfolder
- packageA
- packageB
For the maven api i had updated the pom.xml inside packageA and left everything else as is and that seemed to work. And the maven reports are created inside packageA/target
Alternatively, is there a way that I can use the maven reports to visualise inside vscode?
Environment (please complete the following information, if relevant):
Additional comments
I feel it must be something to do with the remote wsl?
The text was updated successfully, but these errors were encountered: