| Hi Folks,
Any contributions need to happen asap in order to complete the legal process before the release. Even if you don't have a fully working plugin, it's better to get it submitted than wait until it's too late.
A reminder that to contribute to PTP, you need to create a bug in Bugzilla (you will need to get a Bugzilla id first from here: https://bugs.eclipse.org/bugs/createaccount.cgi). When you have an account, open a bug against Tools/PTP and whatever component is appropriate (probably *Core* in this case). Choose a severity of "enhancement" and some appropriate summary and a description.You can then attach a patch to the bug, either as a file you've already created, or from the clipboard if you're filing the bug using Mylyn. Please generate the patch using the "Team>Create Patch..." menu.
You will be required to submit a signed Employee Consent Form ( http://www.eclipse.org/legal/committer_process/employer_consent.pdf) the first time you contribute something. If you're planning a submission (even if it's some time in the future) I suggest getting this form signed *now* since in many organizations it can take some time.
Thanks, Greg On Oct 7, 2009, at 3:01 AM, Siew Hoon Leong wrote:
Hi Thomas and Al,
The way LRZ modified JSch(0.1.41) is simply to extend globus support.
Like Thomas says, we have to replace the current JSch plugin
com.jcraft.jsch_{version}. In addition, a Globus plugin is created
(only required if one wishes to have gsissh support).
Without tje globus plugin, the existing JSch features will continue to
function as usual.
I am not sure if this is the best way to go. As far as I can tell from
JSch style of coding, they seem to prefer a one jar solution where all
dependent libraries are modified and
integrated into Package com.jcraft.
Yes, I would try to integrate it to PTP 3.0 (on my TODO).
Cheers,
Cerlane
Albert L. Rossi wrote:
Hello Thomas,
These are valid points which I would have had to deal with if I were to modify our (NCSA) "plug-in" as well, which currently neither defines nor contributes to extension points (the original work I did on extending Jsch with the org.globus security packages was not directed primarily at Eclipse development).
At this point I am not sure what route the consensus wishes to take on this, though, so I will defer to others for a decision (perhaps we can discuss this on the next call).
thank you, Al
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
"History does not repeat itself, but often it rhymes." (attr. Mark Twain)
----- Thomas Köckerbauer <tkoeck@xxxxxxxxxx> wrote:
Hello
There is also something like this in g-Eclipse (this was also created on
request by LRZ), there is a patched plugin at
http://savannah.fzk.de/cgi-
bin/viewcvs.cgi/fzk/geclipse/geclipse/development/com.jcraft.jsch/
This in this case it adds the globus toolkit as source for the certificate but
this can easily be extended to use other x509 certificates.
The only problem about that is that the original jsch plugin does not provide
any extension point to add such a functionality since it only packages the
jsch jar file (which can also not be extended by that functionality using a a
plugin fragment because of the way it resolves classes).
So the only way to get it running is to replace the normal Eclipse jsch plugin
completely.
The Eclipse way to integrate the functionality, which would be the most
desirable, would be to change the normal Eclipse jsch plugin to provide some
mechanism to extend it. If you are planing to go into that direction please
keep me updated because I would also like to use that solution in g-Eclipse
then.
Kind Regards,
Thomas
On Tuesday 06 October 2009 16:11:07 Albert L. Rossi wrote:
Hi Cerlane,
Thanks for your note. I'm posting this reply to the group because I
believe it will be of general interest.
Several years ago I hacked up a version of JSch to support X.509
certificates, because I needed it for a workflow system and file transport
library I have developed here at NCSA. Greg Watson expressed an interest
in making this available to PTP, which would require me to do a little bit
of refactoring.
However, if you already have such a plug-in for PTP 2.1, I'm sure that
integrating it directly into PTP 3.0 would be the easiest route!
Best,
Al Rossi
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
"History does not repeat itself, but often it rhymes." (attr. Mark Twain)
----- Siew Hoon Leong <Siew-Hoon.Leong@xxxxxx> wrote:
Hi,
I am Cerlane from LRZ. I understand from Guisseppe (Cineca) that you are
working on a JSCH plugin that supports X.509. In fact, I have already
done and integrated it into PTP 2.1 approximately two months ago.
Is this of interest to you?
rgds,
Cerlane
Albert L. Rossi wrote:
Hello everyone,
My name is Al(bert) Rossi; I am a Research Programmer at NCSA (National
Center for Supercomputing Applications) at U. of Illinois, Urbana,
currently working as a member of the Blue Waters software team. I have
been developing full-time in Java for a little over 7 years now, and in
Eclipse for about 4.
As a new participant in ptp-dev, my current, modest goal is to
contribute the missing launch functionality to the PBSResourceManager
plug-ins (org.eclipse.ptp.rm.pbs.proxy, org.eclipse.ptp.rm.pbs.core,
org.eclipse.ptp.rm.pbs.ui).
If anyone else is already working on this, or wishes to collaborate, I
would be quite happy to discuss this with her.
Thank you for your attention,
Al
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
"History does not repeat itself, but often it rhymes." (attr. Mark
Twain) _______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|
