Question

When creating a new project in Flash Builder, how does it determine which sdk libraries to include in the build path?

If I create a new plain Actionscript project and select Flex 4.1 the following libraries show up in the build path:

• playerglobal
• textLayout
• osmf
• flash-integration
• flex
• utilities

If I go back and switch to Flex 3.5 it only includes:

• playerglobal
• flex
• utilities

If I make a new Flex Web project and select Flex 3.5 it includes:

• playerglobal
• framework
• automation
• automation_agent
• automation_dmv
• automation_flashflexkit
• datavisualization
• qtp
• rpc
• utilities

Are these values hardcoded in Flash Builder or is it somehow reading them from the SDK config files? I looked through all the xml config files like flex-config.xml and air-config.xml and it doesn’t look like this information exists anywhere.

Thanks.

Answer 1

After a lot of trial and error and some inspection with a decompiler I have the answer:

1. Flash Builder loads either the flex-config.xml or air-config.xml file (depending on the project type) from the sdk frameworks directory.
2. It goes through each entry listed in library-path and library-external-path adds it to the classpath if it is a SWC. If the entry is a directory it scans that directory for SWCs and includes them.
3. Each project type has a hardcoded list of exclusions which tell Flash Builder which SWCs to leave out of the classpath. For a plain actionscript project this list has 17 items. For a Flex Web project the list consists only of flex.swc. This list of exclusions is written to the .actionScriptProperties file.
4. Any remaining (not excluded) SWCs are automatically added to the classpath. No entry is necessary in the .actionScriptProperties file. (i.e. You can throw any file with a .swc extension in the frameworks/libs directory and Flash Builder will include it.)