I am also getting an "internal compiler error" with FB 4.5. Log file listing is below. Before I was getting this error, I was upgrading my project from 4.0 to 4.5. In 4.0 it built and ran fine. In 4.5, I got 109 compiler errors.
!ENTRY com.adobe.flexbuilder.project 4 43 2011-06-20 10:15:36.645
!MESSAGE Uncaught exception in compiler
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:319)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:129)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 0)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:575)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:350)
at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:187)
Based on what I've read so far this type of error is pretty esoteric and most people have solved it by stumbling around in the dark until they trip over the cause.
Maybe the best solution would be to simply rebuild the module and hope that whatever compiler idiosyncrasy was being triggered in the original code is not repeated in the new module.
I've seen this error once before in a project where [ was being used incorrectly.
If you've narrowed it down to a module, then you could try removing components from the module and adding them one by one to see where the error is. Then take a closer look at that file.
I understand that might not be ideal, but like you said, this is an error seen rarely.
The last post only applies to BadgerJeff.
Scott, your error is related to CSS styles - style name related to background color? Can you post the CSS pieces in that module?
Unfortunately, I have over 300 modules. I don't have the time to hunt down an incorrect '['. Also, what if it's not a bad '['...this search could take nearly forever. In my opinion, this should be the job of the compiler, like all of the other compilers that I have used! When there is incorrect syntax, the compiler should find and mark it, not die.
> the compiler should find and mark it, not di
Yes, this is a compiler bug for sure. No disagreements there. My suggestion was only a workaround - till you get a fix.
Well, I finally bit the bullet and re-wrote the Module in question as a custom component and although the code, except for the header is essentially identical, the compile completes with no errors.
Out of curiosity, were you able to simply cut and paste and change the header structure? Did you do a dif comparison between the two files to see if there was anything different outside the header? Sounds like one I would not want to run into!
In your case, does re-introducing the backgroundColor attribute re-create the problem?
Yes, I created a custom component of type Canvas and then cut and pasted everything after the <Module> header and before the </Module> tag into the
Canvas container and was off to the races with no problems.
The new components header looks like this:
<mx:Canvas xmlns:mx="http://www.adobe.com/2006/mxml" width="718" height="1046" backgroundColor="#FCF9EC">
... so I'm not sure whart you mean by adding or removing the backgroundColor style.
Recently I had "An internal build error has occurred" too. However it has different stack strace than Scott showed. The stack trace was very similar to the one described in this discussion - http://forums.adobe.com/message/2331334 (flex2.compiler.mxml.lang.StandardDefs.isIUIComponent) . However for some reason I am not able to reply to that discussion so I decided to post my findings here. I hope they may be useful to somebody . So the problem in my case was that I had some Event tags declared in Metadata section of an mxml. However these events were not referenced anywhere in the mxml. This resulted in failing every second eclipse clean of a project that has the project, where mxml file was defined, as dependency.