The experiment indicates to me that the proxy cannot base itself on the
project nature. It appears that the remote proxy should be used, if
present, for all accesses.
Seem reasonable?
Sorry, I don't understand what you mean. Are you saying the
getFileProxy(IProject project) method needs to be re-written not to base
on the proxy? Or that the per-nature extension shouldn't look at the
nature?
That it shouldn't look at the nature. If one can use the filesystem drop
down to create the remote project, then there is no special wizard
needed and there is no nature requirement.
I think the URI string already has service name (e.g. remote tools)
already encoded into it, so maybe you could use that instead of the
nature to determine which connection service to use?
Yes, I think that may be the better way to do this. The extension would
then specify which connections it supports rather than natures.
- Corey
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev