Here is the actual output for that issue:

[asdoc] 
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
Error: Can not resolve a multiname reference unambiguously.
spark.components:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/experimental/src/spark/components/Alert.as)
and mx.controls:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/mx/src/mx/controls/Alert.as)
are available.

I can fix this by prefixing the only call to Alert in
WindowedApplication.as (on line 1939) with 'mx.controls.

EdB



On Tue, May 21, 2013 at 7:22 PM, Alex Harui <aha...@adobe.com> wrote:
>
>
> On 5/21/13 9:55 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
>>>>
>>>>2) the build fails because it sees 2 versions of the Alert class (in
>>>>experimental and in MX): prefixing the only call to Alert on line 1939
>>>>of airspark::spark.components.WindowedApplication with 'mx.controls.'
>>>>seems to fix this. Does that make sense and should I commit that
>>>>change?
>>> I suppose, but doesn't this mean that lots of other folks will have this
>>> problem?  Can we/should we change the name of the class in experimental?
>>
>>I wasn't seeing this in my code, it popped up while building the asdoc
>>target of the SDK ant build.xml. If you like, I can reproduce the
>>error and get you the actual error text?
> That would be great, or I'll try to find time later.  Smells like a
> compiler issue, but hopefully only for apps that try to use both Alerts,
> which should be rare.
>
> -Alex
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Reply via email to