[ https://issues.jboss.org/browse/JBIDE-18219?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18219: ------------------------------------ For JBT, we copy entire build folders so we get all the metadata. For example: http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-... http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.... Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows: {code:title=jenkins job name :: github branch@SHA :: github commit/SHA} jbosstools-vpe_41 :: origin/jbosstools-4.1.x@86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3... {code} For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files: JBDS entries are simple: {code:title=github branch@SHA} origin/jbosstools-4.2.x@5327ccb62016547090c569dafa272f99e59b4bc8 {code} But JBT ones are more complex because of how they're collected: {code:title=project-name , plugin-whose-MANIFEST.MF-is-checked , plugin-version , SHA , github branch@SHA , github URL for the source zip with SHA , source zip w/o path } jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730... , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip ... jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598@9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a50... , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)