Because we publish our extensions as standalone extensions, it theoretically is possible to end up with different versions of the individual libraries on the classpath. Therefore it is useful to log (or somehow expose, e.g. as the tracer version) the exact library version used.
This was already implemented for inferred-spans by generating a textual resource containing the version. The way this was implemented was brittle though, as I broke it by removing all other resources while upgrading to async-profiler 3.
This PR makes accessing the version simpler to use by letting gradle generate a java source exposing the project version.
I've added this functionality to our library-packaging-convetions to make it available to all our libraries.
Because we publish our extensions as standalone extensions, it theoretically is possible to end up with different versions of the individual libraries on the classpath. Therefore it is useful to log (or somehow expose, e.g. as the tracer version) the exact library version used.
This was already implemented for
inferred-spansby generating a textual resource containing the version. The way this was implemented was brittle though, as I broke it by removing all other resources while upgrading to async-profiler 3.This PR makes accessing the version simpler to use by letting gradle generate a java source exposing the project version. I've added this functionality to our
library-packaging-convetionsto make it available to all our libraries.