Community
Participate
Working Groups
There are a number of adopters who consume the legacy TM Terminal feature in diverse environments. It would be good migrating them to the TE Terminals. For this, a "standalone" feature is needed with installs only the TE Terminal (and its connectors) but not the rest of the TE dependencies and CDT.
Added o.e.tcf.te.terminals.feature and o.e.tcf.te.terminals.sdk.feature. http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/commit/?id=4ac13a65c01a4aeaeb08355ca99f915f1f84c736
Can you please expose the 2 new features on the TCF nightly update site: http://download.eclipse.org/tools/tcf/builds/development/nightly I suggest doing a new category "Terminal" with the 2 features below.
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/commit/?id=06fb56cc7578fac139036f267849cdeff2e304d9
Created attachment 222974 [details] Screenshot of install dialog Looks good - but I have 2 more requests: 1. The "Terminal" category name is too broad when I have multiple repositories enabled. See attached screenshot. Maybe it's better moving the Terminals feature under the "Target Explorer" category after all. 2. I cannot install the "TE Terminals" feature when I do not have CDT (error below). Since cdt.core is a relatively "fat" plugin, I'm wondering whether that dependency could be avoided or made optional ? ----------------snip-install-error---------------- Cannot complete the install because one or more required items could not be found. Software being installed: Target Explorer Terminals 1.1.0.201210300939 (org.eclipse.tcf.te.terminals.feature.feature.group 1.1.0.201210300939) Missing requirement: Target Explorer, Terminals Process Connector 1.1.0.201209290902 (org.eclipse.tcf.te.ui.terminals.process 1.1.0.201209290902) requires 'bundle org.eclipse.cdt.core 5.4.0' but it could not be found Cannot satisfy dependency: From: Target Explorer Terminals 1.1.0.201210300939 (org.eclipse.tcf.te.terminals.feature.feature.group 1.1.0.201210300939) To: org.eclipse.tcf.te.ui.terminals.process [1.1.0.201209290902]
reopening to investigate cdt dependency
Also, when I install the "Terminals" feature only (allowing to pull its required dependencies from the TM and CDT repos), I do not see the Terminals View in Window > Show View.
>I cannot install the "TE Terminals" feature when I do not have CDT (error >below). Since cdt.core is a relatively "fat" plugin, I'm wondering whether >that dependency could be avoided or made optional ? Right, the processes connector is not a user connector. No need to bundle it with the standalone version. This removes the CDT dependency. > I do not see the Terminals View in Window > Show View. View shortcut is contributed to perspective targetID="*". Means it is available for all perspectives. Please run "Reset perspective" to make sure the perspective has revisted the shortcut definitions. >The "Terminal" category name is too broad when I have multiple repositories >enabled. Moved to "Target Explorer" category.
(In reply to comment #7) > > I do not see the Terminals View in Window > Show View. > > View shortcut is contributed to perspective targetID="*". Hm... I'm afraid that this is too broad, it violates the concept of "peaceful coexistence" in products. View Shortcuts should be targeted for the workflows of a particular perspective. A Java or XML developer doesn't want or need a Terminals shortcut (even if he might have terminals installed for something else). Right now, when I install the Terminals Feature only, I do not see the View under Window > Show View > Other ... likely because the View Category is missing. I suggest making the View Category available, but avoid contributing Terminals to all Perspectives.
Reopen to address view shortcuts
Also, "Terminals" is currently contributed to the Java perspective by default. I don't think this is a good idea.
http://git.eclipse.org/c/tcf/org.eclipse.tcf.git/commit/?id=b6823ef48ff63bd867991e81f890efe249d4874d
