We do exactly this. Each module is a project. This allows each developer to create \ compile \ run a project without reference to another dev. We load each module in the app (at runtime) on demand using the moduleLoader. (Watch for the intermittent loader bug and knock on popup bug !)
The down side to this is that we cannot find a way to compile quickly as each project seems to load the jvm for a compile. This is perhaps more apparent in a release build where the compile is done by Ant on a module by module basis rather than the incremental build in Eclipse. It is how ever dog slow when you do a full clean and rebuild. The other issue that we havent yet rectified, is that each dev can have 1..n number of modules and they wont all be the same as we dont manage each dev's workspace through a source code repository. Oh yes, by the time our project is finished we expect to have about 180 or so modules. Hope this helps BOb --- In [email protected], "Richard Rodseth" <[EMAIL PROTECTED]> wrote: > > I can't seem to find much about the pros and cons of having a separate > FlexBuilder project for each module in a modular, extensible app. It > seems you lose the Optimize For Application menu option, but can work > around that with compiler arguments. Besides, I don't think that's > appropriate in my case. > > Any opinions on best practices? >
