[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-13671 at 7/18/13 1:31 PM: ---------------------------------------------------------------- +1 for this to fix I tested this on local builds and it seems to work right: 1. It does generates timetsamps by using commits 2. It is updates feature timestamp with latest plugin timestamp if plugin was changes but feature was not 3. CI/DEV should go after '$\{BUILD_ALIAS} as '$\{BUILD_ALIAS}-$\{CI/DEV}-v'yyyyMMdd-HHmm becuase that would let devs do a local build whatever component they need and it would be picked up even if never build with CI is available form module nightly update site. 4. For those who using nightly update sites to build modules the benefit would be lesser build time when new nightly build is uploaded for module it depends on. was (Author: dgolovin): +1 for this to fix I tested this on local builds and it seems to work right: 1. It does generates timetsamps by using commits 2. It is updates feature timestamp with latest plugin timestamp if plugin was changes but feature was not 3. CI/DEV should go after '${BUILD_ALIAS} as '${BUILD_ALIAS}-${CI/DEV}-v'yyyyMMdd-HHmm becuase that would let devs do a local build whatever component they need and it would be picked up even if never build with CI is available form module nightly update site. 4. For those who using nightly update sites to build modules the benefit would be lesser build time when new nightly build is uploaded for module it depends on. -- 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