Bug 174162 - [terminal][api] Move Terminal Telnet Connector into a separate plugin
Summary: [terminal][api] Move Terminal Telnet Connector into a separate plugin
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 1.0.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks:
 
Reported: 2007-02-14 09:14 EST by Martin Oberhuber CLA
Modified: 2008-08-13 13:20 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-14 09:14:48 EST
The Terminal Telnet Connector, which is currently part of org.eclipse.tm.terminal,  should be moved into a separate plugin and associated with the terminal.view feature.

New plugin name, referenced in org.eclipse.tm.terminal.view-feature:
org.eclipse.tm.terminal.telnet

New package name:
org.eclipse.tm.internal.terminal.telnet
Comment 1 Martin Oberhuber CLA 2007-04-06 16:27:17 EDT
Not sure if this is actually a must have, but it would be nice.
I'd also like to reduce the number of features for the Terminal.
Comment 2 Martin Oberhuber CLA 2007-05-30 07:48:30 EDT
Michael, what do you think... should we go for this in 2.0 and factor out the telnet connection from the Terminal? It would be interesting for e.g. integrating the Terminal with RSE, since in that case we'd only need the widget but not the connectors.

I could do the actual work if you approve.
Comment 3 Michael Scharf CLA 2007-05-30 08:47:34 EDT
The only reason I did not do it was because I was not sure what the impact of this change would be on the automatic build... If you do it, I'll approve....
Comment 4 Martin Oberhuber CLA 2007-06-05 09:06:00 EDT
Plugin splitted. New projects added to PSF and mapfile:
  org.eclipse.tm.terminal.telnet
  org.eclipse.tm.terminal.telnet-feature
Comment 5 Martin Oberhuber CLA 2008-08-13 13:20:31 EDT
[target cleanup] 2.0 RC2 was the original target milestone for this bug