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.
-- To find / play with my SSH deploying, just create a new SSH server.
The code for it is in its own plugin: org.jboss.ide.eclipse.as.ssh. It
needs a bit of polish. The server has no wizard at this point and the
initial requirements / required data must be manually put in the Server
Editor. The host is on page one, where it always is, but the username /
password / hosts file is on the deployment page.
On 11/04/2009 08:48 AM, Max Rydahl Andersen wrote:
On 02-11-2009 23:44, Snjezana Peco wrote:
> I have set RSE SSH server using Galileo SR1 without any issue.
> RSE uses the Eclipse File System (EFS) - see
> 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.
That would require our server adapter to allow deployment to workspace
mapped resources - not sure Rob uses the Resource API.
Even if we don't use RSE directly from our adapter working with the
eclipse file system would open up for some synergy here.
> Maybe JSCH is simpler, but RSE gives us more functionalities.
My biggest grudge with RSE was that it were adding views and searches
that were put in every perspective.
i.e. search contains a Remote system search as the first default
tab...that ain't nice for users. Maybe they fixed that ?
jbosstools-dev mailing list