Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@airavata.apache.org
Date: Mon, 21 Oct 2013 17:38:42 +0000 (UTC)
From: "Lahiru Gunathilake (JIRA)" <jira@apache.org>
To: dev@airavata.apache.org
Message-ID: <JIRA.12664902.1377110463018.98515.1382377122007@arcas>
In-Reply-To: <JIRA.12664902.1377110463018@arcas>
References: <JIRA.12664902.1377110463018@arcas>
Subject: [jira] [Assigned] (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 ]

Lahiru Gunathilake reassigned AIRAVATA-905:
-------------------------------------------

    Assignee: Lahiru Gunathilake

> 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
>
> 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.1#6144)