[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2710: ----------------------------- Description: For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 * SpringSource's Quick Search - JBDS-2686 *TBD* * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802 * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 These are currently unchanged since December when we released JBDS 6.0.0: * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15 Additionally (Target Platform): * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) See comments below for latest site URLs. [1] https://github.com/jbosstools/jbosstools-locus/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4. was: For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible. The current list of Extras/Central connectors that we mirror are: * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081840-rel-r42 or 3.4.2.v201310081834-rel-r43 - JBDS-2486, JBDS-2801 * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 * SpringSource's Quick Search - JBDS-2686 *TBD* * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802 * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709 * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 These are currently unchanged since December when we released JBDS 6.0.0: * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799). * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15 Additionally (Target Platform): * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests) ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want...? JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only): * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3]) * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3]) See comments below for latest site URLs. [1] https://github.com/jbosstools/jbosstools-locus/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit... [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/ ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4. -- 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