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 20:23:07 UTC

[jira] [Resolved] (AIRAVATA-953) Distribute JNLP With Releases

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

Suresh Marru resolved AIRAVATA-953.
-----------------------------------

    Resolution: Fixed

Since this is blocking the release, I temporarily resolved this commit r1550814. This is not a good fix since every build will sign the jars which is CPU intensive. I will resolve this issue but not close it until we find a better solution.

One thought is to come up with a release/dist profile for all of Airavata. Currently doing so will break the integration tests. So we need to come up with a better way of testing integration at the same time keeping the build process small. 

> Distribute JNLP With Releases
> -----------------------------
>
>                 Key: AIRAVATA-953
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-953
>             Project: Airavata
>          Issue Type: Task
>    Affects Versions: 0.10
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>            Priority: Blocker
>             Fix For: 0.11
>
>
> As reported on the User Mailing lists, the JNLP distributed is desired. We deprecated this in 0.9 release. Add the jnlp back into distribution module and include it in releases. 



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