I only addressed this ticket. Lets first assign tickets and probably start progress too, so we do not work on same issues.
I will be focusing on cleaning up the tracking library now and will assign tickets to myself first. Suresh On Aug 7, 2011, at 10:39 AM, Lahiru Gunathilake wrote: > Ohh are you doing those changes too, I am also doing the xbaya changes. > > Lahiru > > On Sun, Aug 7, 2011 at 10:33 AM, Suresh Marru (JIRA) <[email protected]>wrote: > >> >> [ >> https://issues.apache.org/jira/browse/AIRAVATA-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] >> >> Suresh Marru resolved AIRAVATA-60. >> ---------------------------------- >> >> Resolution: Fixed >> Assignee: Suresh Marru >> >> Removed karma client dependencies and load history option from xbaya. Fixed >> with commit 1154709. >> >>> Remove the broken Karma integration with XBaya >>> ---------------------------------------------- >>> >>> Key: AIRAVATA-60 >>> URL: https://issues.apache.org/jira/browse/AIRAVATA-60 >>> Project: Airavata >>> Issue Type: Bug >>> Components: XBaya >>> Reporter: Suresh Marru >>> Assignee: Suresh Marru >>> >>> Airavata WS-Messenger Workflow Tracking schema was integrated with the >> Karma Provenance Collection System [1]. The Karma schema and the system >> evolved with lot of API changes. The current version integrated with XBaya >> is broken. This integration should be removed for now. Karma is a very >> useful and complementing tools for Airavata. In the future, we should >> solicit contributions to integrate latest version of karma with Airavata >> workflow executions. >>> [1] - http://pti.iu.edu/d2i/provenance_karma >> >> -- >> This message is automatically generated by JIRA. >> For more information on JIRA, see: http://www.atlassian.com/software/jira >> >> >> > > > -- > System Analyst Programmer > PTI Lab > Indiana University
