Hello,
I've got the same issue when the team member had clocked shifted by month
ahead ( do not know how why he had it). The quick solution was to shift my
clock ahead as well and after that all files were compiled without any
problem.
But after putting my clock back the problem had reappeared. The
> > : Line 6: The name of this class,
> > 'com.native.components.ScreenElement',
> > conflicts with the name of another class that was loaded,
> > 'com.native.components.ScreenElement'.
> > class com.native.components.ScreenElement {
>
> Previously clearing ASO cache files worked fine, but it
import com.this.that.Thingy;
would do the trick)
This also tends to happen when #include-ing files that perform the "import *"
maneuver.
>
> From: Sam Thorne <[EMAIL PROTECTED]>
> Date: 2006/04/07 Fri PM 01:00:44 CDT
> To: Flashcoders mailing list
> Subject: [Flas
Hi List,
We've been developing an application over here and sending updates to
a colleague, all has been fine until he started getting compilation
errors.
The odd thing is, the class that is supposed to be conflicting, is in
fact conflicting with itself.
: Line 6: The name of this clas
4 matches
Mail list logo
