I’m not sure how to work this out with Alex’s response that the first one wins.
If I’m reading this correctly, I think I have a problem. The javascript does not have qualified class names. RGBColor is just RGBColor in Javascript, and not com.adobe.RGBColor, so the Javascript will not run as it should. FWIW, I just committed my work on externs for CEP to Github here: https://github.com/unhurdle/cep-flexjs I have not yet had a chance to actually use the externs, so I can’t say for sure that it’s actually working, but it LOOKS like it should… ;-) Harbs On Apr 18, 2016, at 6:03 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > The generated JavaScript always includes the full package. If they're in > different packages, there won't be a conflict. > > - Josh > > On Mon, Apr 18, 2016 at 3:25 AM, Harbs <harbs.li...@gmail.com> wrote: > >> I have a related question here. I can test, but if someone knows off-hand, >> it’ll save some work: >> >> How are conflicts in externs handled? >> >> For example, Adobe’s CEP library has an RGBColor class which has four >> attributes (including alpha), but the FlexJS js.swc has an RGBColor class >> which is missing alpha. If both swcs are included in a project, I’d have to >> qualify on of them with the package path. What would that do to the >> resulting Javascript? >> >> Thanks, >> Harbs
