Re: [dsdp-tm-dev] CDT Launch integration

[Greg Watson <g.watson@xxxxxxxxxxxx>]

Martin, Ewa,

It seems like using the jcraft jsch is the preferable way to go for  
ssh support. The ability to execute arbitrary commands on a remote  
machine is exactly what we're after, so we'll keep an eye on the  
repository for your code.

From our examination of RSE it looks like filesystem support is an  
either/or option, with RSE providing less functionality than the core  
filesystem support (correct me if I'm wrong here). Since our  
requirements are for the filesystem to be as transparent as possible,  
we're planning to focus on providing a remote filesystem using the  
core eclipse filesystem support. Hopefully there will be a way to  
utilize this from RSE in the future.

Cheers,

Greg


On Apr 18, 2006, at 10:21 AM, Ewa Matejska wrote:

> Hi,
>
> My plan was to write an RSE SSH Shell Service, time permitting, to use
> with the CDT integration plugin instead of directly invoking ssh.
> However, since it sounds like you've gotten the jcraft jsch plugin
> integrated into RSE, I'll wait for that work to be submitted and I'll
> default invoking ssh directly for now.
>
> Thanks,
> Ewa.
>
> -----Original Message-----
> From: dsdp-tm-dev-bounces@xxxxxxxxxxx
> [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber,  
> Martin
> Sent: Tuesday, April 18, 2006 2:05 AM
> To: Target Management developer discussions
> Subject: RE: [dsdp-tm-dev] CDT Launch integration
>
> Hi Greg,
>
> I believe that Ewa is using an external ssh program as channel.
>
> I have written an initial RSE integration for the internal jcraft
> jsch plugin that comes with Eclipse team support. My integration
> currently provides an RSE command view through the jsch channel.
> I'm going to post my contribution as a bugzilla entry, to be
> added to the RSE CVS Repository.
>
> The RSE's command channel can then be used to execute arbitrary
> (also user-defined) commands on the remote side.
>
> An additional ssh service for sftp (integrated with RSE files
> support) will be very simple to do.
>
> Plain scp is harder since there is no standard for the shell
> commands to execute for directory listings, so I'm not planning
> this now.
>
> Cheers,
> Martin
> --
> Martin Oberhuber - WindRiver, Austria
> +43(662)457915-85
>
>
> > -----Original Message-----
> > From: dsdp-tm-dev-bounces@xxxxxxxxxxx
> > [mailto:dsdp-tm-dev-bounces@xxxxxxxxxxx] On Behalf Of Greg Watson
> > Sent: Monday, April 17, 2006 8:44 PM
> > To: Target Management developer discussions
> > Cc: Tianchao Li
> > Subject: Re: [dsdp-tm-dev] CDT Launch integration
> >
> > Ewa,
> >
> > Are you checking your code into CVS anywhere? We're looking at using
> > SSH for remote build/command execution and I'd prefer not to re-
> > implement anything you've already done.
> >
> > Regards,
> >
> > Greg
> >
> > On Apr 17, 2006, at 11:23 AM, Ewa Matejska wrote:
> >
> > > Hi Mikhail,
> > >
> > > Yes...I've been working on the CDT/RSE Integration.  I'm focusing
> > > on using gdbserver with ssh.  I will be posting a more thorough
> > > description of my status within the next couple days with screen
> > > shots.  The integration introduces an experimental "C/C++ Remote
> > > Application" launch configuration.
> > >
> > > Thanks,
> > > Ewa.
> > >
> > > From: dsdp-tm-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tm-dev-
> > > bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
> > > Sent: Monday, April 17, 2006 10:12 AM
> > > To: Target Management developer discussions
> > > Subject: [dsdp-tm-dev] CDT Launch integration
> > >
> > > Hi Martin,
> > >
> > > Is there any progress on this?
> > > I am currently considering to add an experimental remote launcher
> > > to the CDT. The RSE and gdbserver seem like a natural choice for
> > > the reference implementation. I haven't tried the RSE yet, but we
> > > can combine our efforts and come up with a better solution.
> > >
> > > Thanks,
> > > Mikhail Khodjaiants
> > > _______________________________________________
> > > dsdp-tm-dev mailing list
> > > dsdp-tm-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> >
> > _______________________________________________
> > dsdp-tm-dev mailing list
> > dsdp-tm-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev
> _______________________________________________
> dsdp-tm-dev mailing list
> dsdp-tm-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-tm-dev