Closed turkcankeskin closed 4 months ago
That is very subtle. I think it should probably always just use https
.
The change to https was good, but the url is still 404. I've found the correct url (https://raw.githubusercontent.com/cobertura/cobertura/master/cobertura/src/site/htdocs/xml/coverage-04.dtd
) , but will need to submit a new PR to update it.
I'm scanning my iOS project with sonar-swift.sh using sonarqube.
slather coverage --input-format profdata --cobertura-xml --output-directory sonar-reports --workspace test.xcworkspace --scheme test test.xcodeproj
It gives Cobertura XML Output directly in my cobertura.xml output.
<?xml version="1.0"?><!DOCTYPE coverage SYSTEM "http://cobertura.sourceforge.net/xml/coverage-04.dtd">
But later when I run sonar-scanner
sonar-scanner -Dsonar.host.url=https://sonarqube.xxx.com/ -Dsonar.login=**** -Dsonar.projectKey=test -Dsonar.qualitygate.wait=true -Dsonar.qualitygate.timeout=600 --define sonar.projectVersion=19.2.0
It gives an error as an exception. I think "https://cobertura.sourceforge.net/xml/coverage-04.dtd" should be used here instead of "http://cobertura.sourceforge.net/xml/coverage-04.dtd"
Is there a parameter for https when creating cobertura.xml in slather? because http://cobertura.sourceforge.net/xml/coverage-04.dtd is a 301 redirect.