[ https://issues.jboss.org/browse/JBTM-1902?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1902: ------------------------------------- Amos, Can you take a look at this as I don't have time at the moment. We already have the buildnumber-maven-plugin in our root pom and it is now set to a version that supports git. We also seem to have the scm block set in the root pom. However, ${buildNumber} is still not resolving. We don't have it configured as it suggests in the following doc, which may be the problem. However, I have tried configuring it as suggested, but it is still not being resolved. http://mojo.codehaus.org/buildnumber-maven-plugin/usage.html Also, I think we need the following config, when you do get it working: {code} <configuration> <!-- gives us a short SHA1 instead of the full commit id --> <shortRevisionLength>5</shortRevisionLength> <!-- allows us to do a build with un-committed files. Essential for development --> <doCheck>false</doCheck> <!-- Doesn't do a git update during build. Essential for development --> <doUpdate>false</doUpdate> </configuration> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira