Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Fri, 28 Mar 2014 15:58:16 +0000 (UTC)
From: "Chathuri Wimalasena (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12664902.1377110463018.25123.1396022296545@arcas>
In-Reply-To: <JIRA.12664902.1377110463018@arcas>
References: <JIRA.12664902.1377110463018@arcas>
Subject: [jira] [Updated] (AIRAVATA-905) Unify SSH Libraries across Airavata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AIRAVATA-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chathuri Wimalasena updated AIRAVATA-905:
-----------------------------------------

    Fix Version/s: 0.13

> Unify SSH Libraries across Airavata 
> ------------------------------------
>
>                 Key: AIRAVATA-905
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-905
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Suresh Marru
>            Assignee: Lahiru Gunathilake
>             Fix For: 0.13
>
>
> Airavata currently has dependencies to J2SSH and JCRAFT ssh libraries. There seems to be no good reason or advantages of one over another. Just to keep it simple, it might be good to pick one and stick to that library. How about JCraft? 


--
This message was sent by Atlassian JIRA
(v6.2#6252)