Try running Menu, Project, Clean
I tried that earlier today but I still get them. I don't think it causes any problems it is just annoying!!! Thanks!!!
Have an Ordinary Day...
Same problem here, very annoying. Everything has started when I've tried to rename some of my .mxml components, it seems that the problem is related to the projet itself, and not the eclipse workspace.
Yes, I am now getting the same error - but slightly different wording
Removing compile problem markers (Time of error: blah blah blah...)
The details section states:
An internal error occurred during "Removing compiler problem markers".
I'm able to compile the same code with no problem from the command line on a Linux box. Running the clean comand doesn't fix this unfortunately.
Some background info: I'm running a FDS project against a JBoss server on a windows XP machine.
So, I deleted my project and shut down flex builder. Then removed the project files (.actionScriptProperties, .project, & .flexProperties) and removed the project folder from the flex.war folder in the jboss server. Restarted Flex Builder and created a new project the same way the project was built. And wa-la the problem is gone.
So, something has gone bad with the project, but I am not sure what because a look a the previous project files and they all seem normal. I was having problems with the project trying to create the "Output Directory" early, but a rebuild of the project seemed to fix that too.
hope this helps.
Any one got a solution to this, its happening in my Flex Bulider 2 for windows as well.
I got mine to quit popping up that error by uninstalling Aptana and Subversion. I then reinstalled subversion without the popup coming back. Unfortunately, subversion keeps telling me that it's too old of a client to work with the repository and I'm running version 1.0.3!
I fixed this by closing FB2, renaming the file C:\Documents and Settings\<My Username>\My Documents\Flex Builder 2\.metadata\.plugins\org.eclipse.core.resources\.projects\<My Project>\.markes so it wouldn't find it and restarting FB2.
It may also delete your bookmarks and breakpoints.
Good tip. This worked for me too, thanks
Can i just add a solution to the suggestions here? i was having this problem also, and though none of these suggestions were working for me, i found a suggestion at flexcoders that so far seems to work - credit to Laurent Fontvielle:
I've got the same problem.
It seems to be a bug with FlexBuilder when you change the "Flex
applications" of your project properties.
You have to edit the file ".actionScriptProperties" located in your
project root folder.
There is the following section:
Maybe there is an entry <application path=...> corresponding to an old
setting. Correct it. Then close project and re-open it.
I'm pretty sure the bug being discussed here has been fixed in Flex Builder 2.0.1, which was released as a free upgrade the other day.
I just encountered the same error on Flex Builder 2.0.1 and it wont go away.
hawkfanxity, did you try the workaround mentioned by Wigg above? "I fixed this by closing FB2, renaming the file C:\Documents and Settings\<My Username>\My Documents\Flex Builder 2\.metadata\.plugins\org.eclipse.core.resources\.projects\<My Project>\.markes so it wouldn't find it and restarting FB2.
"It may also delete your bookmarks and breakpoints."
The bug that existed in FB 2.0 and was fixed in FB 2.0.1 was that at certain times, such as when starting a new compile, FB would clear out the old markers, but there was a race condition between two threads, so the thread that was trying to delete the old markers would sometimes fail.
However, if the markers themselves, as stored in .markers, are corrupt, then that's a separate issue. Wigg's workaround would seem to imply that somehow the markers got corrupted. Give it a try.
This fixed the problem but I was just saying that the fix for this has not been made in Flex Builder 2.0.1.
None of these solutions are working for me. I'm in Flex 2.0.1 but it started after I installed FB 3.
I am on Flex Builder 2.0.1 Eclipse plugin (2.0.155577 version) and I am also victim to this problem.
I had located file .markers at slightly different location:
c:\<My workspace dir> >\.metadata\.plugins\org.eclipse.core.resources\.projects\<My project>\.markers
Erasing this file does nothing.. It is recreated again with a new compilation and this vicious error "Removing compiler problem markers" still remains.
I guess, I am ready to move to Flex 3 Beta 1 now =)
Phew, sorry I was mistaken, clearing the file .markers at the location I had mentioned above had fixed the error Removing compiler problem markers".
Flex 3 Beta 1 can wait for now.
I had the same problem caused by attempting to install flex builder 3 plugin on the Gallileo release of Eclipse. Reverting back to Ganymede the problem persisted in the workspace. It was also very annoying 'cause my current workspace has about 16 projects the majority of which had this issue. I've succesfully got things back up and running and subversion behalving properly and up to date. I used the method decribed above and renamed the .marker files in all of the affected projects. I'm concerned though about the ramifications of doing this.
Does anyone know clearly what purpose(s) these .marker files serve, or can someone point me to the documentation that would explain?
I also got this problem by using Flex Builder 3.2 in Eclipse Gallileo (3.5.1). Going back to Eclipse 3.4.2 and reinstalling Flex Builder did _not_ fix the problem. Deleting the .marker files in the .metadata folder of the workspace (as described by another poster) was the only way I could fix it. Presumably, creating a new workspace and getting from source control again would also fix it because the new workspace would not have .marker files yet.
Only thing hat fixed it for me was creating a new workspace and reimport the projects there.
Can you believe that this is still present in Flash Builder 4.6. Seems like bug fixing is not part of Adobe's release process as I see the same bugs mentioned in these forums again and again over years and years. I am quite convinced that Adobe doesn't ever look at these forums.
We have to remove .marker file from all projects inside, in particular main project and its dependent library projects , make sure you close your Eclipse IDE and do , as it will recreate at the time of closing
That worked for me in Flash Builder 4.7
-------- Adobe Flash Builder 4.7\.metadata\.plugins\org.eclipse.core.resources\.projects\<every Project>
I too facing this same problem but I dont know why this issue occur, removing .marker also wont help. I have fixed by deleting the project and re-import it into flash builder.
That worked for me in Flash Builder 4.7
I just stumbled upon this error when I had written some faulty xml, then commented it out.
private function MyFuncSetEditorSettings(param0:Object, caller:ComponentEditor, options:Object):void
var menu:String = '';/*
menu += '<menu>';
menu += ' <menu label="Use" default="contextmenu"/>';
menu += ' <menu type="separator"/>';
menu += ' <component name="showversions" id="_showversions_" label="Show all versions">';
menu += ' <option id="menupopup" name="menupopup">';
menu += ' <![CDATA[<menu><component name="comparetopreviousversion" id="_comparetopreviousversion_" label="Compare to previous version" /></menu>]]>';
menu += ' </option>';
menu += ' </component>';
menu += ' <component name="comparetopreviousversion" id="_comparetopreviousversion_" label="Compare to previous version"/>';
menu += '</menu>';*/
It seems the CDATA part was breaking Flash Builder insanely giving the Removing compiler problem markers.
The solution was to remove the CDATA-part and in order to get the error messages go away in Flash Builder 4.6 and 4.7. You had to click Problems tab in bottom, then on the I (other problems) you simply right click and delete the problems
Then it should be working.