It was missed when implementing JCasC compatibility (commit 9272245acc2dc0f2d1cef4f7ca99b30706c6e60d).
This fixes the stacktrace being logged to the Jenkins log when a user opened the global config page at http:///configure. This was only a warning and should not have had any functional impact.
It was missed when implementing JCasC compatibility (commit 9272245acc2dc0f2d1cef4f7ca99b30706c6e60d).
This fixes the stacktrace being logged to the Jenkins log when a user opened the global config page at http:///configure. This was only a warning and should not have had any functional impact.
For more details see: https://jenkins.io/redirect/developer/class-is-missing-descriptor