In SQ 4.2, we removed the JavaFile & related classes to replace them by standard "resource" classes. As a consequence, at every analysis, the batch tries to do a conversion if it detects that the project still has old java-like keys. This logic is old and painful, and we don't want to port it on the Compute Engine stack introduced in SQ 5.2.
On a SQ 5.2+ instance, this has the following consequences for projects that have been analysed for the last time in a SQ 4.2+ instance:
- it's possible to access the project in the Web UI, but some services won't work correctly (like the measure drilldown)
- if such a project is reanalysed, then:
- all its issues will be considered as new (so all comments, false-positive, ...etc will be lost)
- differential for some metrics will look strange
Because we won't port this "conversion" logic to Compute Engine stack, we should display a clear message during the migration to 5.2 if we detect that there are still some projects (in the DB) that have components with the old java-like key format.
We detected that the following projects have not been analysed on a SonarQube version greater than 4.2 (included):
As a consequence, some features of the Web UI will be broken for them, and any new analysis will consider all issues as new issues.