Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
Adobe Flex SDK 3.6 (Release)
-
None
-
None
-
Affected OS(s): Windows
Affected OS(s): Windows 7
Language Found: English
Description
Steps to reproduce:
(see Adobe's "Compiling modules" http://livedocs.adobe.com/flex/3/html/help.html?content=modular_4.html for background on the mxmlc option use for modules)
1. Create an application and a module that both use a particular class.
2. Build the application using mxmlc with -incremental and -link-report
3. Build the module using mxmlc with -incremental and -load-externs, supplying it the link report from the application build
4. Remove the class from the application, but leave it in the module.
5. Build the application using mxmlc with -incremental and -link-report. The class will be gone from the link report and the application's swf
6. Build the module using mxmlc with -incremental and -load-externs, supplying it the link report from the application build
Actual Results:
mxmlc indicates that the module "is up-to-date and does not have to be rebuilt". When you run the app and load the module, the module instance isn't created.
Expected Results:
mxmlc reads the link report and the incremental build cache, figures out that a needed class is missing, and builds it and adds it to the swf. When you run the app and load the module, it works normally.
Workaround (if any):
Before building the modules, if the link report from the application build has changed, delete the modules' incremental build caches. That's not a great workaround, as for many projects (e.g. where the main application contains something that changes automatically every build like a version number) it will mean the modules can't ever build incrementally.
Reproduced in:
- Version 3.5.0 build 12683
- Version 3.6.0 build 16995
on Windows 7, Linux