Marvin:

I think that on a Mac OS the same Flash Player is used on Safari and
Firefox so your process wouldn't work.

Oh well all is well right now.

-AP

On Fri, Jul 24, 2009 at 10:17 PM, Marvin Froeder<[email protected]> wrote:
> Well, to check browser caching issue just try the SWF built on your machine
> in another that everything is OK.
> Still, I few your machine is the problem =D
> May be time to format c: ? =D
>
>
> VELO
>
> On Fri, Jul 24, 2009 at 10:09 PM, aparrish <[email protected]> wrote:
>>
>> Guys:
>>
>> Taking your advice on the sanity check I have downloaded all source
>> code from SVN fresh on two new machines and the build executed well
>> and did not exhibit the same behavior. Good that it works for some of
>> the developers, but bad because it still doesn't work for two of us.
>>
>> I am trying your suggestions and just saw it work on my machine. One
>> of the steps I executed was noted here:
>>
>> http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html
>>
>> Is it possible that clearing your browser's cache does not clear out a
>> bad module that was loaded into it? I think that early on in the
>> process I loaded a module built from 3.3 of the SDK or something and
>> then kept recompiling locally, but never thought to blow this cache
>> away.
>>
>> Just vote as to what you think - I sure hope that is it. I will spend
>> some more time working on the process this weekend, but I am going to
>> go forward with this assumption until I prove it wrong.
>>
>> Cheers and Thanks for the support!
>> Adam
>>
>> On Jul 24, 3:12 pm, Logan Allred <[email protected]> wrote:
>> > On Fri, Jul 24, 2009 at 12:46 PM, aparrish<[email protected]> wrote:
>> > > We have successfully reproduced the full build and the recreation of
>> > > the problem on another machine. So machine specifics are now no longer
>> > > being factored into the mix in my opinion.
>> >
>> > Same symptoms? Maven build fails, but FB build succeeds? Are you
>> > launching the apps the same?
>> >
>> > Sanity checks:
>> > Make sure you start with clean builds: manually delete bin-debug (or
>> > output folder) in FB, make sure you run mvn clean
>> > May want to check out a 2nd copy of the code from your scm just to
>> > make sure there aren't any weird hidden code diffs.
>> >
>> > Some other things to try if you get desperate:
>> > Take the dumped config from FB and flex-mojos and run it in the
>> > command line compiler. Tweak the settings until you figure out which
>> > difference is causing the problem
>> >
>> > Logan
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to