[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21233: ------------------------------------ Occurs to me the only reason to KEEP this targetplatforms/jbosstoolstarget/neon URL is so that old JBT releases (4.3.0) can automatically link to the LATEST TP (4.52.x) rather than the one against which it was built. But since an existing JBT user will have http://download.jboss.org/jbosstools/mars/stable/updates/ in their Eclipse, which will be updated to point at BOTH a newer JBT (4.3.1) and a newer TP (4.52.x), we achieve the same thing. Note too that there's no JBDS equivalent targetplatforms/jbdevstudiotarget/neon URL because (for the same reason) we don't need it. We just update https://devstudio.redhat.com/9.0/stable/updates/ with the latest JBDS and TP, and bob's your uncle, all is well -- latest updates delivered and no new clutter in Available Software Sites. Bottom line: we're doing something different for JBT than for JBDS, and the net is more maintenance and more Available Software Sites clutter. Surely we should follow the path of "less work, cleaner list of Avail Software Sites" that we use for JBDS when building JBT, too? Have I missed a reason for keeping this extra URL that provides some value we're not achieving some other way? -- This message was sent by Atlassian JIRA (v6.4.11#64026)