It seems to be unnecessary clutter in the jar root.
The version is already easily discoverable by people who want to find it via META-INF/MANIFEST.MF.
Proposal 1: Move it to the io.opentelemetry.instrumentation.auto package
Proposal 2: Remove it, and use "Implementation-Version" from MANIFEST.MF
Traditionally the reason for using a version file over MANIFEST.MF is that it survives in fat jars. I'm not sure if we have this problem with vendors consuming/wrapping the agent jar? Is that a feature that it will then log the vendor's "Implementation-Version"? Or would it still be useful to have a separate file to track the opentelemetry agent version?
It seems to be unnecessary clutter in the jar root.
The version is already easily discoverable by people who want to find it via
META-INF/MANIFEST.MF.Proposal 1: Move it to the
io.opentelemetry.instrumentation.autopackageProposal 2: Remove it, and use "Implementation-Version" from
MANIFEST.MFTraditionally the reason for using a version file over
MANIFEST.MFis that it survives in fat jars. I'm not sure if we have this problem with vendors consuming/wrapping the agent jar? Is that a feature that it will then log the vendor's "Implementation-Version"? Or would it still be useful to have a separate file to track the opentelemetry agent version?