Do you have another Eclipse builder (Project properties -> Builders) that updates a file in the project?
Can you post your Flash Builder log file? (workspace/.metadata/.log)
The only builder thats in there is Flex, which is ticked.
How do I post the log?
If it isn't too big, you can post the contents inline in your reply.
Or you can either attach the file (or is attaching still disabled?) as a .txt file to your reply or post it on Adobe share.
I see two problems here:
1. At some point, the Subclipse plugin was running into an error preventing Flash Builder from creating the output directory. The side effect of this would be the exact problem you are facing.
2. When you changed a compiler setting, it was unable to overwrite the existing HTML wrapper file - html-template/history/history.css.
The second is definitely a bug on our side, we should be handling this more gracefully. Would it be possible to file a bug for this? Or if you could recall what setting you changed in the compiler property change?
Hi thanks for your reply.
Please file a bug yourself, I have wasted enough time on reporting > 10 bugs (none resolved so far) without any improvement for me.
Re the compiler setting I can only recall fixing the source path for the data-vis components, which is broken by default.
Let me know what other info you need.
Anirudh, did you file a bug report? Wow, cool font now that I copied your name from your profile..
Not yet. Like you suspected in the other posts, many of us are really busy with MAX.
I've flagged this though and will file the bug and circle back with the id here.
P.S: Cool font indeed.
Flash Builder Developer
To be honest, what I find quite frustrating though, is the fact that actual business application development does not happen with the latest and greatest features of Flex (like you are show-casing at MAX).
We build stuff with 3.5, and while Adobe throws a great amount of energy at running ahead by including more features and cool things into their tools, they oversee that the road they have created, and which is being wandered on by thousands of developers, is still pretty bumpy.
Before we ask for more cool stuff, we want the tooling and the SDK to be usable. And that means fixing those thousands of bugs that we report to Adobe.
Just closing and deferring them is not the solution, although it might be a very attractive solution for your product leads.
We pay good money for your software products, and honestly, the support we get in this forum is moderate. I can easily paste here tens of links to bugs and forum posts that just dont get answered or processed.
When I compare this to other solution providers, lets say the IBM ILOG Flex Components, then I have to say the difference is dramatic. Their forum help is nothing short of fantastic. Within days they have answered all of my questions -- with code samples and really good explanations, too.
Please feel free to forward this to Mr Shorten or other product leads, since I know that throwing my frustration at you is not fair.
Anyway, the refresh/build problem just occured again. I checked my log, but the last entry in there is from yesterday, so it seems to happen without a log message being generated.
I was working on some code in a library project, that is linked from our main project. The main project keeps on refreshing and building.