An Internal Build Error Has Occurred Flex 4
wacky will happen in a project or the workspace itself that causes the following message to appear: "An internal build error has occurred. See the error log for more information." In some cases, a refresh and/or clean of the project in question is enough to straighten things out. But if that were always the case, this would be a very short blog entry, and that's not really my style.I recently encountered the "internal build error" monster when working with a Flex module I hadn't touched in months. I simply opened it up and tried to build it, and I was instantly on my way to bang-my-head-against-my-desk-in-frustration territory. Nothing about the project had changed, so all signs pointed to something in the development environment. But what? Step one was to figure out how to "See the error log for more information." There is no apparent indication of where to find this mythical error log, and my best guess (C:\Program Files\Adobe\Flash Builder...?) was a no-go. Luckily I stumbled across an entry over at the 9MMedia Blog which pointed me to the folder {workspace}\.metadata - ah, yes, I recall now that Eclipse loves organizing everything under a workspace. Fair enough.Upon finding the log, I was greeted by a particularly inscrutable error message:!MESSAGE Uncaught exception in compiler !STACK 0 java.lang.IllegalArgumentException: Comparison method violates its general contract! {lengthy stack trace}Gee, I didn't mean to violate anyone's contract.From here, it was back to Google to find this thread on an Adobe forum. It seems there is an issue with backward compatibility in JDK 7. The proposed solution was to add a line to the -vmargs section of the flashbuilder.ini file (this one is, for us Windows folks, found under C:\Program Files\Adobe\Flash Builder)...-Djava.util.Arrays.useLegacyMergeSort=trueRestart Eclipse/Flash Builder, and voila! No more "internal build error" nonsense, which allows us developers to address all kinds of other nonsense.Happy coding! Comments (1) | Print | Send | | del.icio.us | Digg It! | Linking Blogs | 3305 Views Comments (Comment Moderation is enabled. Your comment will not appear until approved.) [Add Comment] Josh, I've been getting this error several times a day ever since upgrading from 4.6 to 4.7 on Windows Vista. I applied your fix to the .ini file this morning, and it seems to have done the trick. Thanks for sharing! # Posted By Jay Wood | 11/7/13 8:16 PM [Add Comment] Calendar << September 2016 >> Sun Mon Tue Wed Thu Fri Sat ����123 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 � Links designery26 Recent Entries N
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Flash Builder http://www.joshknopp.com/blog/index.cfm/2013/3/6/Fixed-An-internal-build-error-has-occurred - Internal Build Error / Classes Must Not Be Nested up vote 0 down vote favorite I've been working on a Flash Builder project for about a week and occasionally encounter one of these two errors when I build: An internal build error has occurred. See the error log for more information. 1131: Classes must not be nested. A quick Project > Clean fixes http://stackoverflow.com/questions/13960232/flash-builder-internal-build-error-classes-must-not-be-nested things up. When I opened my project this morning and tried to build it, I received the internal build error again. This time, however, Project > Clean results in 5 separate "Classes must not be nested" errors, all pointing to my main class declaration. Running Project > Clean again leads back to the internal build error. If I Clean again, I get the 5 class errors again, and so on. I'm using Flash Builder 4.6, Flex 4.6, and AIR 3.5. I haven't made any changes to my codebase since yesterday. Any ideas what might be causing this? actionscript-3 flex air flash-builder share|improve this question asked Dec 19 '12 at 20:00 ced 12 You can try to build your app with ant task to see if problem lies withing flash builder or in your project. If ant task will run successfully, then you have to double-check your project settings like sdk version, referenced libs and sources and so on. If that doesn't help, you can try delete and import project again. And finally reinstalling flash builder. –user1875642 Dec 19 '12 at 20:08 do you use the include dire
here for a quick overview of the site Help Center Detailed answers to any http://stackoverflow.com/questions/20830579/eclipse-indigo-with-flash-builder-4-7-plugin-cannot-use-apache-flex-sdk-only-ado questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack an internal Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Eclipse Indigo with Flash Builder 4.7 plugin cannot use Apache Flex SDK only Adobe 4.6 up vote 0 down vote favorite 1 I have installed Flash Builder 4.7 plugin an internal build into Eclipse Indigo JEE (both of them 64 bit version). I can build flex or air projects with built in Adobe Flex SDK 4.6 without any problems, but after switch project to Apache SDK (i was trying 4.9 and 4.11), my compiler gives me an error: An internal build error has occurred. See the error log for more information. Unknown Flex Problem Error Log eclipse.buildId=M20120208-0800 java.version=1.7.0_05 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product This is a continuation of log file C:\dev\ws_3.7\.metadata\.bak_0.log Created Time: 2013-12-29 21:12:24.581 Error Sun Dec 29 21:59:26 GMT 2013 Uncaught exception in compiler java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.TimSort.mergeHi(Unknown Source) at java.util.TimSort.mergeAt(Unknown Source) at java.util.TimSort.mergeCollapse(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at flex2.compiler.swc.SwcGroup.updateMaps(SwcGroup.java:281) at flex2.compiler.swc.SwcGroup.