No, this isn't the case... I've set up two brand new projects to test this and 
the issue still occurs when I target the 3.5 SDK.  The Flex project has a 
single mxml application and the library contains a single class which is 
imported... error still occurs.


Brendan



--- In [email protected], Oleg Sivokon <olegsivo...@...> wrote:
>
> Hi, yes, I remember this error mentioned few times, I think it was related
> to use of manifest files, where some classes would get referenced twice.
> Does you project deal with that? Or, maybe somehow else imports the same
> classes twice?
>


Reply via email to