Have you tried Target Management (Remote Server Explorer) included in Eclipse IDE for Java EE Developers? Among other things, RSH contains SSH Services. SSH Services API provides deploying an exploded/unexploded archive to an SSH server like deploying to the local file system. See http://www.eclipse.org/dsdp/tm or open the RSE perspective in Eclipse IDE for Java EE Developers and try to add a new connection. Snjeza Rob Stryker wrote: > (This may not be of interest to everyone, but just thought I'd share it. > Also seeking ideas) > > So I spent the better part of this week working on refining some of the > as-tools deployment api's and trying not to break anything (or if you > know me at all, purposely breaking things). I made a new plugin to hold > what is effectively an ssh deploy-only server. There's pretty much no UI > right now and everything's hard-coded, but I've gotten my first ssh > deployment working. ;) > > None of this is in svn yet, but the one use-case I've gotten covered and > working is a zipped wtp-type project. So any project, a web project, ear > project, bpel / esb project, if the server has a property set to force > zipping of deployments, can now be deployed over ssh to some box that > you control. > > Again, it's not in svn yet, and the UI is horrendous (read: not made at > all really) but the underlying APIs are there and I'll work on refining > it tomorrow to squeeze it into svn in some non-disgusting fashion. > > ** I was wondering if anyone had any good suggestions or what types of > settings you'd need for this type of server other than just host, > username, password, and hosts file. What type of functionality would you > want the server to provide you with if you were going to be deploying > remotely repeatedly? > > Thanks in advance. > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

The remote SSH code that Snjezana mentioned looked very very weird to me. Instead I used the JSCH code directly and basically initiate scp commands.

I started it as it's own server but made sure to craft the code in a way so that I could simply add it to current servers as an option at will. So that's the next task. =]

I have set RSE SSH server using Galileo SR1 without any issue. RSE uses the Eclipse File System (EFS) - see http://wiki.eclipse.org/EFS and http://wiki.eclipse.org/EFS#Remote_System_Explorer_.28SSH.2C_FTP.2C_dstor... It is the same API that is used for the Eclipse local file system. The same API can be used to add a local deployment, SSH , FTP, Eclipse dstore or some deployment using a server contributed to RSE. Maybe JSCH is simpler, but RSE gives us more functionalities. Snjeza Max Rydahl Andersen wrote: > I looked at that once long time ago (M6 of Galileo) and it was very > weird to me - but they might have fixed that stuff > so I would need to look at it again. > > Rob - did you try it ? > > About your initial mail, then I don't think this should be a different > server *type*, shouldn't it just be an option > on a server to what way they wish to start/stop/deploy to it ? > > /max > > > >> Have you tried Target Management (Remote Server Explorer) included in >> Eclipse IDE for Java EE Developers? Among other things, RSH contains SSH >> Services. SSH Services API provides deploying an exploded/unexploded >> archive to an SSH server like deploying to the local file system. See >> http://www.eclipse.org/dsdp/tm or open the RSE perspective in Eclipse >> IDE for Java EE Developers and try to add a new connection. >> >> Snjeza >> >> Rob Stryker wrote: >> >> >> >>> (This may not be of interest to everyone, but just thought I'd share it. >>> Also seeking ideas) >>> >>> So I spent the better part of this week working on refining some of the >>> as-tools deployment api's and trying not to break anything (or if you >>> know me at all, purposely breaking things). I made a new plugin to hold >>> what is effectively an ssh deploy-only server. There's pretty much no UI >>> right now and everything's hard-coded, but I've gotten my first ssh >>> deployment working. ;) >>> >>> None of this is in svn yet, but the one use-case I've gotten covered and >>> working is a zipped wtp-type project. So any project, a web project, ear >>> project, bpel / esb project, if the server has a property set to force >>> zipping of deployments, can now be deployed over ssh to some box that >>> you control. >>> >>> Again, it's not in svn yet, and the UI is horrendous (read: not made at >>> all really) but the underlying APIs are there and I'll work on refining >>> it tomorrow to squeeze it into svn in some non-disgusting fashion. >>> >>> ** I was wondering if anyone had any good suggestions or what types of >>> settings you'd need for this type of server other than just host, >>> username, password, and hosts file. What type of functionality would you >>> want the server to provide you with if you were going to be deploying >>> remotely repeatedly? >>> >>> Thanks in advance. >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >>> >>> >>> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> >> >> > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

I have set RSE SSH server using Galileo SR1 without any issue. RSE uses the Eclipse File System (EFS) - see http://wiki.eclipse.org/EFS and http://wiki.eclipse.org/EFS#Remote_System_Explorer_.28SSH.2C_FTP.2C_dstor... It is the same API that is used for the Eclipse local file system. The same API can be used to add a local deployment, SSH , FTP, Eclipse dstore or some deployment using a server contributed to RSE.

Maybe JSCH is simpler, but RSE gives us more functionalities.

I do not use the Resource API at all really. The Module Factories do to create their IModuleResource[] tree, but once you get down to publishing I never deal with the resource API at all. I'm not sure how using the Resource API is superior to simple file copies. I could maybe understand it if the deploy folder / destination were in the workspace, as the workspace would need to be aware of those files existence. However a simple refresh on a project would accomplish the same thing after using the generic java.io APIs. I see no obvious superiority of the Resource API to warrant using it.