I know Spring Roo doesn't support multi project yet, but I need two sites to run on the same models / controllers (about 50 models) and on the same database without having to update models on both applications.
I was thinking that I could generate the models and controllers in a master project and have the child projects use symlinked models and controllers. This still feels like I'm duplicating a lot of code, is there a better way to achieve the same result?
If you are looking into having a UI customization for different clients for the same product built using Spring Roo, you can simply achieve the above with the use of a Version Control System.
Just fork your main source for two branches and keep updating the trunk and pull them to the branches when there is a change to the modules, while maintaining the individual UI customizations in the branches.
Additionally, you can wait for Spring Roo 1.2 release which has already promised multi-module maven project support (ROO-120) for Spring Roo projects.
Cheers and all the best with Roo!