[kepler-dev] [Bug 5416] New: downloaded modules by Kepler module manager should know the path of main Kepler installation.

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: downloaded modules by Kepler module manager should
                    know the path of main Kepler installation.
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: build system
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: jianwu at sdsc.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


In Kepler 2.2, new modules downloaded by Kepler module manager are located at
~/KeplerData/kepler.modules/, which includes both zip file and unzipped module
fold. Some modules have their own executable files which need the classes in
main Kepler installation, such as the *.sh files in master-slave module. To
correctly start these executables, they need to know the path of main Kepler
installation, namely the path where kepler.sh is located when users install
Kepler 2.2. Since the installation paths for Kepler 2.2 could be different,
there is no conventional path for it.

I found the build-area folder in ~/KeplerData/kepler.modules/, it could be a
good place to put a info file, e.g. keplerPath.txt, in this folder telling the
Kepler installation path. By this way, downloaded modules from Kepler module
manager will be able to find the classes in main Kepler installation.

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