BuilderLibrary is a subclass of flex2.tools.oem.Library. It does not have new methods but it overrides Library.compile().BuilderLibrary.compile() processes the compc command-line arguments in BuilderConfiguration before calling super.compile(). The argument processing extraces the following arguments: 1. dump-config: creates a File (absolute or relative to the current working directory) - same behavior as compc. 2. compiler.debug: calls Configuration.enableDebugging(). 3. compiler.accessible: calls Configuration.enableAccessibility(). 4. compiler.strict: calls Configuration.enableStrictChecking(). 5. help: do nothing. 6. output/directory: calls Library.setOutput() if -directory=false. Calls Library.setDirectory if -directory=true. The output is absolute or relative to the current working directory) - same behavior as compc. 7. version: do nothing. 8. include-classes: calls Library.addComponent(). 9. include-file: calls Library.addArchiveFile(). The file is absolute or relative to the current working directory - same behavior as compc. 10. include-namespaces: calls Library.addComponent(). 11. include-resource-bundles: calls Library.addResourceBundle(). 12. include-sources: calls Library.addComponent(). No valid compc command-line arguments should cause this argument processing to fail. FB should expect the argument processing to be consistent with compc (including absolute and relative paths). Any inconsistencies are considered Compiler API bugs. If the behavior is the same but it's incorrect, it's considered a compc command-line parsing bug. The only two execeptions are -help and -version. -help and -version will not do anything. FB should use F1 for help and `About Flex Builder' for showing compiler version.
All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.