After install, it reports itself as 1.0.0. I should think it would be auto-set via Maven, so might be something that needs adjusting, or perhaps the “rebuild” didn’t really hit all the modules in some way.
Environment
None
Activity
Rod WiddowsonJune 25, 2022 at 1:15 PM
… its the trailing slash on the name (again)
Rod WiddowsonJune 25, 2022 at 11:06 AM
So, even with a manifest it fails. So what it wrong with the manifest
The reason why this is the case is that I failed to update the version in the properties file while cranking that release out.
I have amended the process to check for that in future release.
However the property is suppose to be a fallback only if the version from the pom file is not found. So the important work is to diagnose this - we have an entire jar whose only purpose is to return the version and it isn't doing that.
After install, it reports itself as 1.0.0. I should think it would be auto-set via Maven, so might be something that needs adjusting, or perhaps the “rebuild” didn’t really hit all the modules in some way.