[ https://issues.jboss.org/browse/JBIDE-22696?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22696: ------------------------------------ {code} [INFO] --- maven-antrun-plugin:1.3:run (process-about-mapping) @ com.jboss.devstudio.core --- [INFO] Executing tasks [copy] Copying 1 file to /mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/plugins/com.jboss.devstudio.core [echo] product.releaseNumber = 10.0.1.AM1 [echo] buildQualifier = v20160613-2041 [echo] product.buildTimeStamp = ${product.buildTimeStamp} {code} Code for this is in https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... Build id is most likely coming from this plugin, com.jboss.devstudio.core, which has not been updated since 20160613-2041, so this is arguably correct. Build date appears to be missing (regex match is failing to derive it from the plugin version) -- so we need that fixed. But should that be the current date (eg., 20160708), or the last mod date of the repo, 20160613-2041 ? [~akazakov] what do you think? Should the branding plugin use jgit timestamp, or the current timestamp, to align with the version of the installer jar? -- This message was sent by Atlassian JIRA (v6.4.11#64026)