The builder does not delete any file but renames them:
Given a deleted/renamed Java source file "path.to.MyClass.java" in the generator scope, the builder looks for all potential AS3 outputs using the pattern "path.to.MyClass[$...][Base].as" and renames them to "path.to.MyClass[$...][Base].as.[millis].hid". It take cares of package translators (if any) and configured AS3 output dir for the given Java source.
If any other AS3 file hold a reference to renamed classes, this operation will lead to compilation errors, which is the main goal of this improvement.
This behavior can potentially lead to errors, for example renaming an AS3 file named "path.to.MyClass$Something.as", while this file hasn't been generated but written by end. This is, however, a very unlikely case, and it is always possible to revert the operation.
Franck Wolff added a comment - 12/May/12 07:33 PM The builder does not delete any file but renames them:
Given a deleted/renamed Java source file "path.to.MyClass.java" in the generator scope, the builder looks for all potential AS3 outputs using the pattern "path.to.MyClass[$...][Base].as" and renames them to "path.to.MyClass[$...][Base].as.[millis].hid". It take cares of package translators (if any) and configured AS3 output dir for the given Java source.
If any other AS3 file hold a reference to renamed classes, this operation will lead to compilation errors, which is the main goal of this improvement.
This behavior can potentially lead to errors, for example renaming an AS3 file named "path.to.MyClass$Something.as", while this file hasn't been generated but written by end. This is, however, a very unlikely case, and it is always possible to revert the operation.
Improvement
Resolved
Minor
Deleted and renamed classes should be cleaned
Given a deleted/renamed Java source file "path.to.MyClass.java" in the generator scope, the builder looks for all potential AS3 outputs using the pattern "path.to.MyClass[$...][Base].as" and renames them to "path.to.MyClass[$...][Base].as.[millis].hid". It take cares of package translators (if any) and configured AS3 output dir for the given Java source.
If any other AS3 file hold a reference to renamed classes, this operation will lead to compilation errors, which is the main goal of this improvement.
This behavior can potentially lead to errors, for example renaming an AS3 file named "path.to.MyClass$Something.as", while this file hasn't been generated but written by end. This is, however, a very unlikely case, and it is always possible to revert the operation.