[jbosstools-issues] [JBoss JIRA] (JBIDE-9905) should be investigated main updatesites could be composite content sites to allow for proper rollback

[ https://issues.jboss.org/browse/JBIDE-9905?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9905: ----------------------------------- metadata == artifacts.jar/content.jar. It's a digest of the feature.xml and manifest.mf files in the feature/plugin jars, plus crap like license/copyright details so it can be presented when installing before pulling down the actual feature jars. So, if your metadata for JBDS 4.1.0 is of size X, then adding 4.0.0 and 4.1.1 to the same site will make the initial download of metadata 3X in size. And then ultimately the user will only do an install that's the same size as if there was only 4.1.0 on the site. I can easily make this change - it's just a couple files [1], [2]. [1] https://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/4... [2] https://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/4... But it'll make searching for updates longer by a factor of as many old versions as we include. Same story for the Extras site [3], [4] - two files that need updating to pull in the additional metadata: [3] https://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/4... [4] https://svn.jboss.org/repos/devstudio/trunk/devstudio.jboss.com/updates/4... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira