-
Notifications
You must be signed in to change notification settings - Fork 143
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
Support relative path in explicit ErrorLog value #1074
Labels
Comments
The same issue affects the Razor property as well. |
should this be supported in the S4NET or rather in the SQ plugin @pavel-mikula-sonarsource ? |
This should be fixed on S4NET side as the target file also contains the ultimate source of truth about the base path that the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
#1015 fixed an issue that the explicit
ErrorLog
property provided by a user wasn't handled properly. Since 5.3.0 we do accept user-provided values.Problem is that we only support absolute paths now because
ErrorLog
could be relative to the project directory. Such value gets propagated to theProjectInfo.xml
as a relative path but they don't share the same base when processing.Originally reported on community forum
Reproducer
To reproduce the issue, add relative
ErrorLog
property to a project file:Then
end
step will produce a warning:Workaround
To workaround the issue, you can set absolute path in the
ErrorLog
property:The text was updated successfully, but these errors were encountered: