[ https://issues.jboss.org/browse/JBIDE-16376?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16376: ------------------------------------ The zips are collected to make (in theory) the update site reproduceable by collecting snapshots of the upstream update sites that are composited into the aggregate. If we move to a publish-each-project-independently-to-dl.jb.org or publish-each-project-to-nexus model, this stops being required. Also, we've never had to rebuild an update site from its component child update sites, despite having the capacity to do so. The only zip that's *actually used* regularly is the hibernate tools one, which gets renamed and published along with the JBT aggregate zip: http://www.jboss.org/tools/download/stable/4_1 via: https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... I have quietly stopped including that zip for 4.2.0.Alpha1, however, hoping that people will not notice its disappearance and instead just download the JBT aggregate zip if they really need something for offline use. I've also tried repeatedly to remove it for past releases but there's been some push back on that from people who REALLY love hibernatetools and don't want to download 418M of JBT when they only need 78M of hibernatetools. As you can see from the clickthrough stats on http://www.jboss.org/tools/download/stable/4_1 people do want that zip, about 50% as much as those that want the full JBT zip. See also stats here: http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.1.x/ (300/wk JBT, 150/wk hibernatetools) -- 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