To generate Session.OSS_DRIVER_COORDINATES we load a properties file that was generated by the build, and append -shaded if we detect that Netty classes are not in their original package (it can be useful to know that it's the shaded version of the driver, and the artifact version alone can't tell that).
However, in some of our internal builds we append a build number to the version, e.g. 4.0.0-feature+123. The above process produces 4.0.0-feature+123-shaded, which makes Version.parse fail. The shaded artifact is unusable because of that.
A much better solution would be to append -shaded to the artifact id instead. This happens to match the actual value in the POM.