airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Saminda Wijeratne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-669) Separate current Airavata binary distributions to seperate Client & Server binary distributions
Date Tue, 01 Apr 2014 19:08:14 GMT

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

Saminda Wijeratne resolved AIRAVATA-669.
----------------------------------------

    Resolution: Fixed

Resolving this since it was fixed long time ago.

> Separate current Airavata binary distributions to seperate Client & Server binary
distributions
> -----------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-669
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-669
>             Project: Airavata
>          Issue Type: Task
>            Reporter: Saminda Wijeratne
>
> Current binary distribution include both server & client components together. In
order to avoid confusion & unnecessary overhead of retrieving/understanding/configuring
for different stakeholders we can have the following separate binary distributions created
at build-time,
> Airavata server binary distribution  - everything related to hosting an Airavata Server
> XBaya binary distribution              - everything needed for XBaya to run independently
> Airavata client binary distribution   - all the libraries required for a 3rd party client
to use the Airavata API



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

Mime
View raw message