Over 10 years of community discussion and knowledge are maintained here as a read-only archive.
treat the framework SWC as an RSL, PureMVC MultiCore as external, and then place the two of them (along with another other common elements) into a separate Flex Library Project--perhaps called 'common'.
In the main application, should I add the entire project to the library path or just the SWC?
then it's best to just keep modules in the same project and deal with it. -- it seems to me.
Have you read Chapter 30 of the Flex 3.0 Developer's Guide from Adobe? Covers modularity in depth...except cross-project modularity.
If, like me, a person is in a situation where they anticipate resistance to adding yet another thing the developers have to learn (like Ant) or install (replace Stand-alone Flex Builder with Eclipse), then it's best to just keep modules in the same project and deal with it. -- it seems to me.
we have concluded that Flex is not a viable platform for the development of enterprise-grade business applications.