BlazeDS locking $ProjectName-debug folder and not allowing flex builder to build project

Question

Hi all,
Im new to Flex. I'm trying to setup my development environment. What I've noticed is that when blazeds is started and I run a flex project, it creates a folder in the blazeds root folder named $ProjectName-debug (replace $ProjectName with the actual project name). Once this folder is created, and the flash page is accessed, it cannot be deleted until blazeds is actually stopped. The files on that folder seem to be locked. While this folder is locked, eclipse cannot seem to re-build the project (specifically clean). Thus every small change I make to the project, I'm currently having to stop blazeds, clean the flex project, start blazeds, run the flex project.What makes things worse is that I have to start our application along with blazeds so it can retrieve the data from the app (which takes a few minutes).
I'm wondering if other people are having to go through this pain or if they've figured out a way to get around this. I would ideally like to have a way where I'm able to rebuild the project and hit f5 and reload the page and see the changes. I understand this is not possible with debug.
If anyone has figured out a way to incorporate blazeds to their development environment in a more practical way, please let me know. We just switched from tapestry/gwt to flex. We used to be able to update on the go thus development was much simpler.
Regards,
Udam

Answer 1

if you see a red error in your "problems" tab inside
flexbuilder, your project most likely will not be built fully, or
correctly, in that case running that project does not makes sense
at all, you need to make sure "problems" tab is clear of errors
(you might see warnings, but they are not very harmful) .if ther is
no errors, hitting ctrl+B builds the project and choosing Project
--> Clean ... clears output folder and rebuilds the project P.S
Unless you uncheck checkbox that says "automatically build project
after clean".
IMHO, turn off Auto Build and manualy build the project that
will take care of most issues, plus use (project --> clean) when
you need to make sure you have latest build .
Kind Regards
Levan.