Re: [Flashcoders] Duplicate Class errors
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 solution I've found was the PHP script that open file, copy it's content and put it into new filewith the same name ( for automation). Regards, Oleg ___ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
Re: [Flashcoders] Duplicate Class errors
> > : 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 seems it's
> this isn't working now either.
> Unzipping a different copy somewhere else on his machine has also
> failed with the same error.
If you're doing this over a network, this is related to discrepancies
in the system clock. Syncing them fixes the issue.
-K
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
Re: [Flashcoders] Duplicate Class errors
Could it be that some interdependent classes are each importing all of a
package when they only need to import a certain class from them?
I generally run into these problems when trying to run some new AsUnit
TestCases that have sloppy imports in them (i.e.
import com.this.that.*;
when
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: [Flashcoders] Duplicate Class errors
>
> 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 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 seems it's
> this isn't working now either.
> Unzipping a different copy somewhere else on his machine has also
> failed with the same error.
>
> Anyone got any idea what might be happening here?
>
> Regards,
>
> Sam Thorne
> Interaction Design
>
> Web: http://www.native.com/
> Tel: +44 (0)207 588 7970
> Fax: +44 (0)207 588 7971
>
>
> ___
> Flashcoders@chattyfig.figleaf.com
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
--
John Mark Hawley
The Nilbog Group
773.968.4980 (cell)
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
[Flashcoders] Duplicate Class errors
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 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 seems it's
this isn't working now either.
Unzipping a different copy somewhere else on his machine has also
failed with the same error.
Anyone got any idea what might be happening here?
Regards,
Sam Thorne
Interaction Design
Web: http://www.native.com/
Tel: +44 (0)207 588 7970
Fax: +44 (0)207 588 7971
___
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
