If you happen to encounter this error message - "An Internal Build Error has occured. Click here for more information" in your flex builder, the solution you can think of trying are the following:
a) Your code might not have a case for the switch brackets.
switch (value)
{
// No case statements are written below but it has just the switch skeleton
// case '1':
// break;
// default:
// break;
}
b) Try to locate the problem. The problem is thrown by the Flex Compiler. Click on your flex builder menu option Help->About Eclipse SDK-> click on the button "Configuration Details"-> opens up a configuration dialog -> click on the "Error Log" button. You will see the error log on what is happening (why the flex compiler is failing, this is mostly because of Null pointer exception in the compiler code)
c) Change your SDK version. Window -> Preferences -> Flex -> Installed SDKs -> {try a newer version of sdk download it from opensource.adobe.com/flex (look for sdk). Sometimes there could be a problem with a specific version of the sdk and it might be fixed in later versions. So Trying out later versions would help.
d) Another alternate could be to switch the workspace (though not recommended). This could be the last resort for your options. Some times your workspace configuration files might get messed up and you might not have much time to even think further (instead of getting stuck as your compiler wont work). Change your workspace to a brand new one and create your project from scratch (SVN?)
e) Have ANT Script for your project which you can run through command line. So you will atleast know which package has a problem. So you can comment out that package / file for time being to resolve the issue to quickly and get going fast.
2 comments:
This is due to replicating the .actionScriptProperties settings file in SVN. This file should be ignored, so it remains private to each of our respective machines.
This file specifies the target directory for where to put the compiled SWF file. I use it to force the recompiled SWF file to show up in RAILS when I run from localhost, so I get the latest just by refreshing my browser. The file is constructed when you edit the Compiler Build Path in the project properties in Flex Builder. It hard-codes /User/mydir or /Users/yourdir, so when the settings file gets updated from SVN onto the other machine, it points to a directory that doesn't exist.
I put this file on svn:ignore, but I think you have to SVN UP with the file absent to make the file be ignored on your side.
Here's what has to happen:
You copy your file to somewhere (e.g., ~/Desktop).
You SVN RM the .actionScriptProperties file and then commit.
Then SVN UP, and THEN the file should be ignored. At this point, you can copy it back to your working directory, and if you do SVN ST, it should not show up, nor will it be committed any more.
Once the file has been restored to your working directory, then right-click on the Flex project, select Properties, select Build Path, and change the path to /Users/myDir instead /Users/yourDir.
Make sure when you save the project properties, run SVN ST. You should NOT see .actionScriptProperties as being modified. If you do, the svn:ignore didn't stick.
After all this, you should not see the internal compilation error anymore.
Mike,
Thanks for your valuable inputs. I believe the scenario with .actionScriptProperties file vs SVN is a scenario that can be handled by each developer.
I believe when you pull up the flex project properties and choose your appropriate build output path directories after you freshly imported project from svn, it will be overwritten with new values. Yeah svn ignore it. We dont commit these files, they are just used for initial project import, but we customize it with the properties panel on flex project...
this specific internal build error can be simulated with switch: with no case.. not sure if its fixed in the new beta1 flex 4..
thanks again
Post a Comment