Issues on creating new modules.

1) Module specific ant tasks: Where to put ant tasks specific to the new module? It is reasonable to put it in the new module directory. So we need to build in a function in the main build system to execute targets from build files in other modules.

2) Module specific Menu item: one menu item is need to enable my new module. File uiMenuMapping_en_US.properties records the Menu configuration. I found that ppod-gui module put a same file in its module directory. Is it a generic solution for module specific menu item that each module keep its own configuration files?

1) Module specific ant tasks: I made a separate build.xml in master-slave dir, it works.

2) Module specific Menu item: Like pPod, I also have its own uiMenuMappings_en_US.properties. I also moved the class for this menu item from package org.kepler.gui to org.kepler.distributed.

I don’t know whether this way is very accordant to the new build system, but at least it is viable. If anyone is interested, please have a look at it. Better solutions are welcome. Thanks.

P.S.: Maybe we should a detailed guide document (such as FAQ) for new build system developers. I will be glad to contribute some questions.

Hi Jianwu,

1.) I think that your solution for specific ant tasks is a good one, at least for now. Is there further support for this use case that you would like in the build system?

2.) Your solution for menu mappings is also appropriate. In the future, we might consider a more nuanced approach, but for now this is in fact the best way to do it.

Thanks for your response. Currently, my module works fine. If I find more requirements, I will let you know.