[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19776: ------------------------------------ Max, * omitting tm.terminal (plugin) will break Server builds * tm.terminal.feature is the replacement for the ecf.te feature which you explicitly told me to include above. Rob also told me to include this because it includes all the local, ssh, telnet, etc. connectors * tm.terminal.feature includes connector.local, which requires some CDT stuff from within Mars M7, including *platform-specific fragments* But you appear to be saying: * omit tm.terminal; doesn't matter if Server builds break So, assuming you agree that there's an end-user or technical reason stated above, I can include ONLY the tm.terminal plugin for now. Then, you can debate w/ Rob if it makes sense to have JBT Server Tooling also include the new tm.terminal.feature, which includes connector.local, which depends on CDT *platform-specific* fragments being installed too. Note that we currently have NO platform-dependent fragments in the target platform. Adding them will make the TP only buildable on a single platform (like 64-bit Linux). Instead -- if we need this connector.local thing -- we may need to repackage the CDT stuff into an update site (as we've done for Xulrunner) and link to it when building update sites, rather than including it in a TP. Does that make the problem more concise? I hope so, since I've asked if you want to include something that drags in CDT plugins three times now without a concise answer. :( I am asking about it here, not in JBIDE-17686, because whatever we decide affects the contents of the target platform as well as what gets installed along with Server Tools. -- This message was sent by Atlassian JIRA (v6.3.15#6346)