Specifications

145ADOBE FLEX 3
Building and Deploying Adobe Flex 3 Applications
include-libraries library [...]
Links all classes inside a SWC file to the resulting application SWF file, regard-
less of whether or not they are used.
Contrast this option with the library-path option that includes only those
classes that are referenced at compile time.
To link one or more classes whether or not they are used and not an entire SWC
file, use the
includes option.
This option is commonly used to specify resource bundles.
include-resource-bundles bundle [...]
Specifies the resource bundles to link into a resource module. All resource
bundles specified with this option must be in the compiler’s source path. You
specify this using the
source-path compiler option.
For more information on using resource bundles, see “Localizing Flex Applica-
tions” on page 1101 in Adobe Flex 3 Developer Guide.
includes class [...]
Links one or more classes to the resulting application SWF file, whether or not
those classes are required at compile time.
To link an entire SWC file rather than individual classes, use the include-
libraries
option.
incremental=true|false
Enables incremental compilation. For more information, see “About incre-
mental compilation” on page 157.
This option is true by default for the Flex Builder application compiler. For the
command-line compiler, the default is
false. The web-tier compiler uses
incremental compilation by default.
keep-as3-metadata=class_name [...]
Specifies custom metadata that you want to keep. By default, the compiler
keeps the following metadata:
• Bindable
• Managed
• ChangeEvent
• NonCommittingChangeEvent
• Transient
If you want to preserve the default metadata, you should use the += operator
to append your custom metadata, rather than the = operator which replaces
the default metadata.
This is an advanced option. For more information, see “About metadata tags”
on page 33 in Creating and Extending Adobe Flex 3 Components.
Option Description