Open hohwille opened 3 years ago
Also this looks like a promising hint to me: https://github.com/devonfw/sonar-devon4j-plugin/blob/5413bf97221e752c648953ea3cd052c9ec39294d/pom.xml#L145
So for the analysis of this task someone should do this for several SonarQube versions (e.g. 5.6
):
7.9
)sonar:sonar
on it after successful install
build with maven.If this already works fine with 5.6
we can lower minimum version from 7.9
to that version already. Otherwise we need to test other versions in between that range since we found the real minimum version.
Time has passed meanwhile and nobody took action here.
IMHO versions like SonarQube 5.x can be considered obsolete/dead/unsupported.
We could easier raise the sonarQubeMinVersion
property and go forward.
With #5 we entered the SonarQube marketplace and created this configuration: https://github.com/SonarSource/sonar-update-center-properties/blob/master/devon4j.properties
Some projects are using an older version of SonarQube and cannot use our plugin. Analysis of this plugin and its history gave me the impression that we rather accidentally came to the minimum SonarQube version
7.9
. Instead we should test and analyze which version of our plugin is working with which version of SonarQube. If I am correct and we already support lower versions than7.9
, we should update the marketplace entry even for older releases and "fix" this.