[ https://issues.jboss.org/browse/JBDS-2486?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2486: ---------------------------------- OK, so there are a few approaches we can do in general when a mirror includes dupes (or different versions) of upstream reqs: a) mirror everything and deal w/ the duplicates. Hope that nothing bad happens. Less maintenance when producing mirrors. This is generally the process we do today. b) filter it out so that jetty (for VJET) or windowbuilder (for GPE) are only coming from one place: the Kepler mirror. Hope that nothing bad happens. Requires that someone notice that there are dupes after mirroring, and then filters them out from the build.xml script and re-does the mirror. Can be time consuming for large mirrors like WTP or Eclipse, which currently include WAY more than we actually use in the JBT TP, and which contain LOTS of dupes over what's in Kepler itself. c) build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. WDYT, [~maxandersen], [~mickael_istria] ? -- 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