Hi Scott, Where are you currently generating your production builds? Are you using any type of continuous integration server (e.g. CruiseControl, Jenkins)? If so, you should already have a build script being triggered to build out all of the modules and project output. If Ant is getting too messy for that you could consider moving to Gradle.
If you're not using a CI solution right now I'd highly recommend it if nothing else for repeatability of builds. In terms of source control I think you're taking the correct approach in having distinct source folders for the different modules; that definitely helps avoid cross-contamination. For our large Flex apps (similar setup to yours) we have three separate projects set up in FlashBuilder, one for the web app, one for the common library and one for the Air app. That keeps FlashBuilder from letting us pull in incorrect source. In short, it sounds like you're on the right track from a source control standpoint; you just may need some work on the build side to automate the different modules. If you have any questions on the details let me know and I'll see how I can help. -Marty On Fri, Nov 11, 2011 at 1:34 PM, Scott Talsma <[email protected]> wrote: > How is everyone approaching larger projects w/multiple outputs? I have a > Flex app compiled for browser, but it now also has desktop version. The > desktop version has an isolated module that uses AIR extensions for the > database. > Currently, I have three separate projects with the following setup: > WebVersion (outputs web.swf and 2 s:Module swfs for visuals) > -src > --modules > -libs > --src > LocalStorageModule (outputs s:Module that interacts w/sqlite, also includes > unit tests for development in isolation) > -src > --tests > --module > AirVersion (compiles Desktop swf (s:WindowedApplication) and 3 modules, > packaged as .AIR) > -src > -extra src directories: > --webversion/src > --webversion/libs/src > --LocalStorageModule/src/module > I know that I can collapse all three projects together and target only the > files I want in multiple projects. However I need to guantee that no I can > always compile the web version w/o any references to AIR imports creeping > in. Right now I can package my Air version from start to finish via ANT, > and all the extra libraries are setup in a custom project-config.xml file. > There will be mobile versions on the horizon, so this will be only getting > more complicated. ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
