RE: [dsdp-dd-dev] RE: [dsdp-tm-dev] I am working on org.eclipse.t m.term

[Doug Schaefer <DSchaefer@xxxxxxx>]

Thanks, Martin. I think at the end of the day, as long as we can build the
terminal view as a separate feature, and you have your committer access
organized as you need, it doesn't really matter where it resides.

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC Member


> -----Original Message-----
> From: dsdp-dd-dev-bounces@xxxxxxxxxxx [mailto:dsdp-dd-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
> Sent: Tuesday, November 21, 2006 5:20 AM
> To: Target Management developer discussions; Device Debugging developer
> discussions
> Cc: DSDP PMC list
> Subject: [dsdp-dd-dev] RE: [dsdp-tm-dev] I am working on
> org.eclipse.tm.terminal
> 
> Hi Michael,
> 
> first of all thanks for all your great work. Looking at how
> many people CCed on your bugzilla items, I got an impression
> of how hot the terminal is with the community!
> 
> > I'm also not sure if TM is the right place for the terminal.
> > I think is should be independent of TM. Instead TM should use
> > is (see also bug 165177). In any case, it should be possible
> > to use the terminal without any other TM plugins.
> 
> There seems to be still some misunderstanding between what TM
> and RSE is [1]. Target Management is a Project, a plain organizational
> entity. As such, it produces multiple components, some of which
> have no dependencies to anything except the Platform.
> 
> Currently, the TM project provides of the tm.core and tm.rse
> components.
> 
> The tm.core component is meant for base components that can be
> used independently of RSE, and each other. Right now, tm.core
> contains
>   - the terminal
>   - the discovery core component
> There will be no problem providing a separate ZIP download
> for the terminal alone, without any dependencies to RSE.
> 
> With this background, my feeling is that tm.core is the
> right place for the terminal.
> 
> Regarding checkin:
> When you are planning to create multiple plugins, the
> new terminal won't interfere with the old one anyways,
> since the plugin Ids (and thus project Ids) will be
> different. For example:
>    org.eclipse.tm.terminal.core
>    org.eclipse.tm.terminal.view
>    org.eclipse.tm.terminal.connector.serial
>    org.eclipse.tm.terminal.connector.debug
>    org.eclipse.tm.terminal.connector.rse
> 
> These are just random examples. Let's discuss the plugin
> structure on Bugzilla, and check in the code as soon as
> there is sufficient agreement regarding the component
> and plugin split-up.
> 
> References:
> [1] The TM and RSE FAQ also has an item on the differences
>     between TM and RSE:
> 
> http://wiki.eclipse.org/index.php/TM_and_RSE_FAQ#So_what_is_the_differen
> ce_between_TM_and_RSE.3F
> 
> 
> Cheers,
> --
> Martin Oberhuber
> Wind River Systems, Inc.
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
> _______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev