[kepler-users] custom suite and module

[Chad Berkley]

Hey Chris,

Dependencies should trickle down the tree automatically.  If you put 
your module name above *kepler (like you have below), the compile and 
runtime dependencies should be set so that you have access to any module 
underneath yours.

I think you're probably seeing a bug in the actor tree code which is 
actively being developed.  The WRP suite seems to work fine, however. 
I'm not sure why your actor library would be empty.  Aaron, do you have 
any ideas?

At any rate, look at the WRP suite for an example of how to do this.

chad


Chris Weed wrote:
> I am not sure about this, but my suspicion is that my module of code 
> depends on other kepler modules.
> I am guessing I need to make a dependency of my module on them.
> I guess it needs to be a suite to encode these dependencies in the 
> modules.txt file, but I may be wrong there.
> Chris
> 
> On Tue, Nov 17, 2009 at 2:09 PM, Chris Weed <chrisweed at gmail.com 
> <mailto:chrisweed at gmail.com>> wrote:
> 
>     Hi,
>     I create a new module with some actors in it, and I created a suite
>     that includes that module and *kepler in the modules.txt file as
>     follows:
>     testmodule
>     *kepler
> 
> 
>     When I change-to the new suite and try to build it (ant run) the
>     actor selection window is empty.
> 
>     It seems to load ok, when I take my custom module out, and just have
>     *kepler in the modules.txt file.
> 
>     I've attached the build output in kepler_error.txt
>     Chris
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users