[
https://issues.apache.org/jira/browse/FLEX-34858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Tynjala resolved FLEX-34858.
---------------------------------
Resolution: Fixed
Commit:
https://git1-us-west.apache.org/repos/asf?p=flex-sdk.git;a=commit;h=ffdb0714
> Adding a subclass of a Vector's type to the Vector in MXML results in an
> internal build error
> ---------------------------------------------------------------------------------------------
>
> Key: FLEX-34858
> URL: https://issues.apache.org/jira/browse/FLEX-34858
> Project: Apache Flex
> Issue Type: Bug
> Components: MXML Compiler
> Affects Versions: Apache Flex 4.14.1
> Reporter: Josh Tynjala
> Fix For: Apache Flex 4.15.0
>
>
> The subclass doen't get detected as a dependency.
> Example MXML that causes build error:
> <fx:Vector type="mx.core.UIComponent">
> <s:Button/>
> </fx:Vector>
> I discovered that it will work fine if another Button is added elsewhere in
> the MXML document. Somehow the Vector's items aren't being checked for
> dependencies.
> It may be fixed by passing the VectorNode to the same analyze() function used
> for ArrayNode in the private DependencyAnalyzer class in InterfaceCompiler at
> the end of the analyze() function for VectorNode. There is no analyze()
> function for ArrayNode, so it must fall back to the version with the
> parameter typed as Node. The analyze() function for VectorNode only grabs the
> Vector's type as a dependency and doesn't look at the items added to the
> Vector.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
