On Fri, Jul 24, 2009 at 12:06 PM, aparrish<[email protected]> wrote: > We all run mac os x. > They are able to build fine. > They are able to load my builds and their builds fine. > I am able to load their builds. > I am not able to load my builds.
When you say load a build, does that mean launch the app/swf in a browser or FP standalone? Do you create a war, do you pass around a zip file of the /target dir? Are all of the compiled .swfs/swcs exactly the same on the different machines? There is something environmental going on if it occasionally fails only on some machines (or it's a bug in the code/race condition). These are tricky to track down. Is the error always the same? It's a runtime error correct, not a compile-time error? How are the compiled stylesheet swfs from the designer distributed (maven, svn, network, ftp, etc.)? Things I can think of: Corrupted artifacts in the local or nexus repo (blowing away the local repo should expose one of these--it will fix the prob or cause a good machine to break) ~/.m2/settings.xml is getting artifacts from differing locations or has some different config Different SDK versions (between machines or between compiled modules) Different security settings Different versions of the Flash Player or debug vs non-debug players Different maven versions (extremely rare unless it's a compile time problem, and then still quite rare) You may need to run maven with the -X output and diff the outputs from the different machines, or attach it here so we can take a peek or something. 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/ -~----------~----~----~----~------~----~------~--~---
