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
{{ message }}
This repository has been archived by the owner on Mar 9, 2023. It is now read-only.
I'm using the latest version of both SQ and this scanner, but it's not picking up the version field from package.json and in SQ I get "unknown version".
If I put sonar.projectVersion in sonarqube.properties then it works, but having to maintain a redundant version field is error-prone.
Is the scanner supposed to pick up the version from package.json?
Note: I'm running the scanner from the command line.
The text was updated successfully, but these errors were encountered:
It seems to only look at the package.json if there is not a properties file (by design). There should be a way to have a properties file and leave out the version or name so it gets picked up from the package.json
I beleive @Cowdrey is right. scanner should give precedence to package,json and pickup version rather from properties file. Its not fair to manually give same version in more than one place.
I'm using the latest version of both SQ and this scanner, but it's not picking up the
version
field frompackage.json
and in SQ I get "unknown version".If I put
sonar.projectVersion
insonarqube.properties
then it works, but having to maintain a redundant version field is error-prone.Is the scanner supposed to pick up the version from
package.json
?Note: I'm running the scanner from the command line.
The text was updated successfully, but these errors were encountered: