[ https://issues.jboss.org/browse/JBIDE-17002?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17002: ------------------------------------ OK so what you wanted was that the new connector entry in the plugin.xml pointed to the default Kepler Central site [0]. [0] http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ But instead of only 3 entries in the generated file, you wanted a custom file which would have to be hand-maintained, and would list a 4th site [1]. [1] http://download.jboss.org/jbosstools/updates/requirements/kepler/java8/ You also wanted a different URL than what I selected [1]. Unfortunately, this was not clear in your comments above, so I was unable to provide you what you wanted. Instead, you got what you requested, to the best of my interpretation as approved via PRs and screenshots above. Is this an important enough issue that it needs to be fixed at the expense of other work I could be doing? If so, please confirm that what I now believe to be your original request (as stated in this comment) is in fact what you want, and reopen this issue to indicate that it is NOT resolved to your satisfaction. If, on the other hand, I have once again failed at psychic debugging, please clarify what you'd like in the plugin.xml file, and what URLs should be in the stable kepler Central composite site. -- We could as well, consider rebuilding the target platform to include this extra collection of patch features, and re-release that as well as a new discovery plugin. That would also guarantee the "internal URL" [1] would never be seen by an end user. -- Please reopen and clarify which route you'd like, or, if this is no longer something that needs to happen, simply close this JIRA. You could also open a NEW one, targetting JBT 4.1.3, if you'd like. -- This message was sent by Atlassian JIRA (v6.2.3#6260)