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 have this plugin and https://github.com/SonarSource/sonar-scanner-gradle in the same classpath.
Both plugins have the very generic /version.txt file in their JAR and read it to find out their own version.
This of course makes one of the plugins misidentify its version, in my case the SonarQube plugin thinks it is version 0.60.3 because this plugin comes first in the classpath.
It would be better to have a more unique name like refreshVersions-version.txt or the file moved to a path under the namespace of this plugin like de/fayard/refreshVersions/core/version.txt to minimize the risk of resource-name-clash with other plugins or libraries.
The text was updated successfully, but these errors were encountered:
I'm not talking about the file where the versions are stored.
I'm talking about the version.txt file that is included in the plugin jar that contains the plugin's version.
I have this plugin and https://github.com/SonarSource/sonar-scanner-gradle in the same classpath.
Both plugins have the very generic
/version.txt
file in their JAR and read it to find out their own version.This of course makes one of the plugins misidentify its version, in my case the SonarQube plugin thinks it is version
0.60.3
because this plugin comes first in the classpath.It would be better to have a more unique name like
refreshVersions-version.txt
or the file moved to a path under the namespace of this plugin likede/fayard/refreshVersions/core/version.txt
to minimize the risk of resource-name-clash with other plugins or libraries.The text was updated successfully, but these errors were encountered: