I am really getting killed here. In community source, I created a new module (new->module) and in that a Hello World Java class . WHen I build the new module does NOT show up in the out->production directory. I have to guess that there is a build script(s) between me and make that is causing this. I am not anxious to plunge into multiple ANT GANT scripts with al their variables and dependencies and all that just to be able to add a module
The HelloWorld module is just a cheap test to try and trouble shoot a problem I had when I tried to add a homegrown unit testing plugin framework and was copying what I saw junit did as far as configuration goes.
In that case I was creating file templates like junit and placing those templates in a directory structure that mimics junits own file structure. Good enough for now. I should say here that I added the my module to the module "plugins" next to all the other plugins and using the project structure screens and declared the dependencies on test-framework and all the rest and implemented JavaTestFramework etc etc and also a proper plugin.xml, the META-INF and added the dependencies therein. All that stuff. Done.
I noticed that despite Community finding my plugin and using its classes, - it knows there's a new test framework in town and shows that to me as a choice in the createTestDialog, build (make) absolutely was not not not transferring (the coimpiled version of) the folder with the source of the plugin from source to out->production . Actually that's a bit of a mystery to me because those classes are being found at runtime.
If you read Practical API Design by Jaroslav Tulach then Iam having an amoeba moment where I am discovsering that how Community gets built and what is happening when I press make-run is markedly different than the mental model I had for it.
Any help here on any aspect of this is so appreciated.