[kepler-dev] Getting rid of CreateModulesBundle

[David Welker]

Actually, ModuleTree is a singleton. The moduleTree instance in 
ModulesTask is just a convenience.

So, the code you would need to use is:

ModuleTree.init();

for( Module m : ModuleTree.instance() )
   // Your work

or

for( Module m : ModulesTree.instance().reverse() )
  // Your work. But iterate in reverse order of priority.

-David
> If you extend ModulesTask, you can use the local variable modulesTree 
> and increment through that.  If you need to access that in kepler, we 
> might need to make a singleton instance or something that you can get at.
>
> chad
>
>
> Daniel Crawl wrote:
>>
>> Hi David,
>>
>> I'm happy to remove it, if you can please suggest an
>> alternative: how can I get a list of modules used
>> (inside a running Kepler)?
>>
>> Thanks,
>>
>>  --dan
>>
>>
>> David Welker wrote:
>>> Hi Daniel,
>>>
>>> I was wondering whether, since CreateModulesBundle is not really 
>>> necessary, whether or not you could remove it in the near future?
>>>
>>> Thanks!
>>> David
>>
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>>
>