Can somebody evaluate the issue? In case the bug will not be evaluated till COB the bug isn't considered as stopper for
release. Thanks.

Of course, the bug would be fixed in patch1.

Now I can not reproduce the issue.
Please provide some additional information:
- NB build number where the issue occurs
- type of project or the project itself
- exact steps to reproduce the issue

  

Sorry, but just by saying you can reproduce it you didn't solve the issue. It is unacceptable to close P1 without 
proper investigation. 

Build is 200804090003

As is dead easy to reproduce. Create new project, choose release configuration, go to project properties and change 
something in c++ settings (for example strip). Close the dialog and click on Clean&Build
And here you are, makefile is deleted and no build is possible.

please provide var/log/messages.log file from your userdir. I can't reproduce this bug with the steps above on my linux
machine.

QA or Developers change bugs' status to INVALID when they can not reproduce the bug and need additional information how
to reproduce the issue and it's a normal process. When submitter provides required information and confirms that bug is
still reproducible he/she also changes status to REOPENED.

I don't think that you should use in your work build 200804090003. First of all it's risky because it's a developer's
build. I use more fresh developer's build 200804180003 and can not reproduce your issue in it with your scenario. Anyway
a bug in  developer's build can not be a showstopper for a product because it's another branch. Please try your scenario
using the latest release candidate from http://download.netbeans.org/netbeans/6.1/rc/ 

Created attachment 60556 [details]
My message.log, it doesn't look to contain something interesting. And I am running Win XP

I deleted Makefile-Release.mk file and I can regenerate it without big problem.
Scenario:
- Create project
- Build project
- Find and delete Makefile-Release.mk and Makefile-Debug.mk files from 'Files' tab
- Build project
==> Build fails
- change something in c++ settings (for example strip)
- Build project
==> project is built. Makefile-Release.mk and Makefile-Debug.mk files is appeared again

luky, can you try to reproduce the bug in RC2? Thanks.

Does actually rc2 support old projects? I am getting feeling it is related to the old 6.0 projects which were converted.
In rc2 I can't even open old project 

To  apepin 
That's not the standard approach. You can close the bug if you investigate and reporter doesn't respond to the request 
for more info. And even in that case it is not ivalid but Works for me. 

OK, here is what is happening:

1) Makefiles are generated when something in the project has changed.
2) The project system doesn't check the state of the generate makefiles before a build.

You can duplicate the problem this way:

1) create a project.
2) build it
3) manually remove on of the generated makefiles
4) Build it again. Now it fails becasue makefile doesn't exists.

To regenerate the deleted makefile, open and OK properties, and build the project.

Will downgrade to P2 as there is a reasonable workaround.

yep, and when you go to the properties again, change something, makefiles are deleted again. Pretty annoying if you 
want know:) 
It's happening in my old 6.0 project converted to 6.1 regurarly. If somebody is in prague office I can show it to you 
right away (office 2304). With RC2 it deletes actually both Debug and Release projects

6.0 projects are compatible with 6.1 and should work fine.

You say the generated makefiles disappear somehow while using the project?

Can you provide the exact steps to reproduce it? What do you do? Clean, build, run, debug, ...?

Will close. No further info to go after. Please reopen if new info resurfaces...