Hi We prefer the patch which is created by using svn diff. In this way, the committer can apply the patch more easily.
BTW, don't forget to grant the ASF license when you submit the patch in the JIRA. Willem Claus Ibsen wrote: > Hi > > This is good so far. > > You could sign up in our JIRA and create a ticket for the request. > http://issues.apache.org/activemq/browse/CAMEL > > And add the code. Then it's easier for us to get the code committed, > as we would like to have a JIRA ticket for the bugs, features, task > etc. that we commit to the code base. > > Also see the contributing guide: > http://activemq.apache.org/camel/contributing.html > > > /Claus Ibsen > Apache Camel Committer > Blog: http://davsclaus.blogspot.com/ > > > > On Thu, Nov 27, 2008 at 12:35 AM, ychawla <[EMAIL PROTECTED]> wrote: >> Actually Step 3 should be this to accomodate those who do not have a >> passphrase on their private key: >> >> if (getConfiguration().getSftpPrivateKeyFile() != null && >> !getConfiguration().getSftpPrivateKeyFile().equals("")) >> { >> if (getConfiguration().getSftpPrivateKeyFilePassphrase() != null >> && !getConfiguration().getSftpPrivateKeyFilePassphrase().equals("")) >> { >> jsch.addIdentity(getConfiguration().getSftpPrivateKeyFile(), >> getConfiguration().getSftpPrivateKeyFilePassphrase()); >> } >> else >> { >> >> jsch.addIdentity(getConfiguration().getSftpPrivateKeyFile()); >> } >> } >> >> Should also mention that the private key file that I had was in openSSH >> format, I can test with a private key in SSH.com format at a later time as >> well. Putty-gen was used to generate all private/public key files and >> Globscape Secure FTP server was the SFTP server. >> >> >> -- >> View this message in context: >> http://www.nabble.com/SFTP-Component-private-key---passphrase-for-connection-tp20711040s22882p20711165.html >> Sent from the Camel - Development mailing list archive at Nabble.com. >> >> >
