[kepler-dev] [Bug 5483] New: Another Kepler GUI will nuke the ~/.kepler/cache generated by the kepler in workflow run engine

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5483

           Summary: Another Kepler GUI will nuke the ~/.kepler/cache
                    generated by the kepler in workflow run engine
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: core
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: tao at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


The workflow run engine embeds a kepler at workflowrunengine/kepler. Now the
workflow run engine runs the kepler by calling the API of the kepler.

I found an issue that if we start another kepler GUI in another location, e.g.
~/project/kepler, the kepler gui will nuke the ~/.kepler/cache directory even
though they are in the same suite. This may cause a problem to run the workflow
run engine. However, if we start the kepler gui from workflowrunengine/kepler,
the kepler gui wouldn't nuke the cache directory generated by the run engine.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.