[kepler-dev] [Bug 4483] Module dependencies in MoML files

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Wed Feb 2 11:57:08 PST 2011


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

Derik Barseghian <barseghian at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barseghian at nceas.ucsb.edu

--- Comment #17 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2011-02-02 11:57:07 PST ---
We no longer write any module dependency info into the moml, but certain things
from modules may still be written into the moml, e.g. provenance recorder and
reporting listener, as mentioned in the original bug.
I think one acceptable way to close this bug is to simply add a warning to the
export action (the way you write moml now) stating that export is lossy, that
module dependency info is not kept -- e.g. if you export to moml from within
the reporting suite, opening that xml file in another suite that lacks
reporting will give errors.

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


More information about the Kepler-dev mailing list