[ https://issues.jboss.org/browse/JBTIS-1023?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBTIS-1023 at 1/24/17 11:10 AM: ------------------------------------------------------------- [~aurelien.pupier] If you're all talking about the jgit timestamp provider we now use in the parent pom for nearly all the jbosstools artifacts, then... see JBIDE-13671. I know the person that implemented it very well. We share a last name. Also a first name. :D The benefit to using jgit timestamps is that you know exactly when the code was last modified, and if you look in the plugin's manifest you can see the SHA used to build the code. From that you can then find the exact commit in github. But if you're going to use the jgit timestamp provider instead of the default one, you should remove the B## suffix since that WILL change with each build and you'll end up with new plugins that are essentially identical but renamed. THAT will be confusing -- how does osgi know which of the two plugins with the same x.y.z.timestamp to use? was (Author: nickboldt): [~aurelien.pupier] If you're all talking about the jgit timestamp provider we now use in the parent pom for nearly all the jbosstools artifacts, then... see JBIDE-13671. I know the person that implemented it very well. We share a last name. Also a first name. :D The benefit to using jgit timestamps is that you know exactly when the code was last modified, and if you look in the plugin's manifest you can see the SHA used to build the code. From that you can then find the exact commit in github. -- This message was sent by Atlassian JIRA (v7.2.3#72005)