You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2013/12/13 17:52:08 UTC

[jira] [Commented] (AIRAVATA-965) Update Airavata JGLOBUS and Unicore jar

    [ https://issues.apache.org/jira/browse/AIRAVATA-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847645#comment-13847645 ] 

Suresh Marru commented on AIRAVATA-965:
---------------------------------------

I do not think it is a good idea to use jgblobus 2.1 yet. I rather suggest to remove unicore from this release since the jglobus 2.1 has too much of untested new code. We might run into unitended side effects with Proxies and GRAM provider. Also, its is not a good idea to base Airavata release on a unreleased dependency. 

> Update Airavata JGLOBUS and Unicore jar 
> ----------------------------------------
>
>                 Key: AIRAVATA-965
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-965
>             Project: Airavata
>          Issue Type: Story
>            Reporter: Raminderjeet Singh
>            Assignee: Raminderjeet Singh
>             Fix For: 0.11
>
>
> To resolve the bouncycastle version conflict, we need to update jglobus to 2.1-rc version(not release yet) and unicore to 1.7. 



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)