[kepler-dev] How to add a new module with recent build?

[David Welker]

Hi Anne,

If you want to have the CP module detected without making a new suite,  
but by editing modules.txt, you can just delete current-suite.txt or  
change the value to "unknown." The thing is, as the system currently  
stands, if current-suite.txt is specified, then in case of a conflict  
between the contents of that suite and modules.txt, the contents of  
the suite are used. So, if you want to just edit modules.txt manually  
without making a new suite, you have to make sure that current- 
suite.txt does not contradict it. This can be done by simply deleting  
it, or changing the contents to "unknown" (either course of action is  
functionally identical).

-David

On Oct 6, 2010, at 3:24 PM, Ngu, Anne Hee Hiong wrote:

> With the most recent checkout (two days ago) of Kepler, I cannot get  
> my own module to compile and run  using the usual "ant run" command  
> in the build-area directory.
>
> For example, I created  my own module called CP a year ago and I  
> used to be able to get it compiled and ran by adding an entry at the  
> top of the list in the  modules.txt file.
> Now, the system cannot detect my module.
>
> I notice that with the new build, there is an additional file called  
> current-suite.txt,  do I need to do something with the current- 
> suite.txt?
>
> Hope someone can enlighten m eon  how to use the new build to  
> include a new module.
>
> Thanks,
> Anne
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev