Yes. It is a blocker for me. I’m not sure what’s different. Yishay is on Windows and I’m on Mac. I recently upgraded from Maverick to Yosemite. Maybe that changed something. Don’t know.
If the multiple-target will solve this problem, good. For now, I just pushed a change to check for all three classes. That fixed it for me. > On Jan 31, 2017, at 3:12 AM, Alex Harui <aha...@adobe.com> wrote: > > > > On 1/30/17, 3:33 PM, "Harbs" <harbs.li...@gmail.com> wrote: >> >> [java] resolved: SWC: [DefinitionPromise "XML", DefinitionPromise >> "QName", DefinitionPromise "XMLList"] >> [java] XML >> [java] QName >> [java] XMLList >> >> >> So, it looks like the order of the classes are indeed XML, QName, XMLList. >> >> Maybe, the cu should be trimmed to make QName the first one before being >> passed to FlexJSProject.isExternalLinkage(). > > And we've finally nailed down the problem... > > Are you using a different version of Java than Yishay? It looks like this > list comes from iterating a HashSet which has no defined order. I > wouldn't want to spend time sorting the list either. > > Is this a blocking issue for you? I hope to finish up the multiple-target > compile soon, maybe this week, which should effectively eliminate this > problem because JS compiles would no longer compile against playerglobal > (they would compile against js.swc). > > Or maybe for now, test not only for Qname, but also XML and XMLList. > > Thoughts? > -Alex >
