On 11/3/14, 12:00 PM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>> >> So it looks to me it is running FalconJX’s compc, not Falcon’s. So the >> issue is probably that FalconJX’s compc doesn’t know how to ignore >> lookupOnly entries. For FlexJS, we are not using COMPC to compile the >>SDK >> so we’ve probably never hit this. >> > >I'll step through FalconJX again, but at some point the stack jumps to >Falcon for the actual compilation, so I'm not sure what I might be able to >achieve on "my" end. For sure, the code jumps to Falcon and Falcon reports the error. I’m thinking that there is a Configuration difference causing whatever logic that determines which files to compile to pick up the lookUpOnly classes. FalconJX code may need to override that Configuration, or override the function that decides to try to compile that file. > >>As this concerns the SDK (the Spark project, kinda central ;-)) and >>Falcon >> >(not FalconJX) I was hoping that someone recognised the >>'MiniDebugTarget' >> >reference and would know why it is still referenced by current SDKs, >>when >> >the code for it was last seen in SDK v. 3.6? >> >> A google search found this: >> https://issues.apache.org/jira/browse/FLEX-20327 >> >> MiniDebugTarget probably needs to be deprecated but we could try >>removing >> it. >> > >As there is no actual code, just a reference to code that was already >removed, the only thing to remove would be those references ... Well, we could remove MiniDebugTarget from the manifest and see what blows up. -Alex
