https://grey-panther.net/2011/02/augmenting-log4j-stack-traces-with-class-versions.html Just another WordPress site Tue, 06 Sep 2011 10:19:25 +0000 hourly 1 https://wordpress.org/?v=6.9 https://grey-panther.net/2011/02/augmenting-log4j-stack-traces-with-class-versions.html#comment-46 Tue, 06 Sep 2011 10:19:25 +0000 https://grey-panther.net/?p=84#comment-46 I also had to solve this (be aware of the exact SCM version running on production) for Java projects. My approach was a bit different:
1. I use Maven to build the projects
2. My project has a multi-module structure
3. I use the maven-buildnumber-plugin to write the SCM (SVN in my case) revision in own of Java module's MANIFEST file (details here http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html)
4. I created a page (or a small section in the footer of the application) which shows the version of as read from the manifest file at runtime.
For snapshot versions (on test environments) I show both the maven POM version and SCM revision, while for released versions I only show the POM version (because I use the maven-release-plugin so I have a SCM TAG created for each released version)

]]>