Created attachment 44576 [details]
screenshot

Can't reproduce with build 070710.

Reproducible in build 200707231200.

Not reproducable with daily builds,
but reproduceable on installer's builds.

I could reproduce the issue with the netbeans extracted from a zip file.
http://bits.nbextras.org/download/6.0/nightly/200708011200/zip/moduleclusters/netbeans-trunk-nightly-200708011200-all-
in-one.zip

So the issue is not the installer`s one...
I`ve tried to disable all unnecessary clusters and left only the following:
platform7
nb6.0
ide8
java1
xml1
apisupport1
enterprise4
soa1
harness
extra


Unfortunately the issue reproduced in this set of clusters as well...

As Kirill suggested, to find out the reason of the issue you can, at first, make a diff of 'daily build' (whatever I 
mean by saying that) and all-in-one zip file.

Fixed in trunk:


/cvs/enterprise/xslt/project/src/org/netbeans/modules/xslt/project/XsltproProjectGenerator.java,v  <-- 
XsltproProjectGenerator.java
new revision: 1.12; previous revision: 1.11
/cvs/enterprise/xslt/project/src/org/netbeans/modules/xslt/project/XsltproProject.java,v  <--  XsltproProject.java
new revision: 1.14; previous revision: 1.13

Reproduced in build 200708200000.

Fixed in trunk:

/cvs/enterprise/xslt/project/src/org/netbeans/modules/xslt/project/XsltproProjectGenerator.java,v  <-- 
XsltproProjectGenerator.java
new revision: 1.14; previous revision: 1.13

But there is still another problem - close action activated on project directory presents "Close 2 projects", 
i.e. there is still problem with projects cache(may be not ProjectManager#dir2Proj).


Could reproduce for bpel, sql, , compapp, uml projects...
It looks like some times the cache ProjectManager#dir2Proj doesn't updated.

For more information see 81039, 57301, 57270, 42422.

jglick I saw that you had actively partcipated in discussion of these issues could you provide the final design(solution).
Now a lot of projects (except j2se, web, and some others) still have this problem. 
What is the best to keep ProjectManager#dir2Proj in actual stage ? (IMO  manual filesystem refresh isn't good solution
and doesn't work well :()

If you see a general problem with project infrastructure please file a clean issue with steps to reproduce in the
projects component.

possibly a duplicate of already filed issue. The project infrastructure weakly references the known projects. 
When you get back to the IDE from other applications, the IDE will try to refresh the status of all FileObjects it
knows. Any deleted folders/files  eventually fire deletion events, however that can be take more time in general than it
takes the user to try creating new project.

You are encouraged to do project delete within the IDE.

in general I'm somewhat skeptical toward this class of issues. How often does it happen in real-life user scenario that
a user decides to delete a project? And create a new one at the same place right away? It looks like a QA-only issue to me.

Fixed in trunk,
enterprise/xslt/project/src/org/netbeans/modules/xslt/project/XsltproProjectGenerator.java  1.14.

It looks like the problem is in ProjectManager#proj2dir cache update,
it's common problem and could be reproduced with number of other projects: (sql, compapp, bpel, uml ) and it's related
to the
issues (81039, 57301, 57270, 42422).

To reproduce the issue one should create new project(any of the mentioned types)
then close it and quickly (depends on system) delete this project from file system, and try to create new one with the
same name.

More over even after manual FS.refresh there is still problem with cache update:
create xslt project
close it
then "quickly" 
delete it from fs
create new xslt project with the same name
invoke popup menu on the project (there is "close 2 projects" point instead close project)

Sorry, the last comment - wrong , I didn't see  mkleint, jglick and my comments :(

jglick, mkleint - I'll look for duplicate issue (now I saw just one and it's marked as fixed - 42422)

mkleint - I'm agree this scenario doesn't looks like from real life but the problem with cache update appears in other
scenario (111892 - Renaming of a BPEL module works incorrectly). It's more real life scenario :)
So currently number of projects have several similar issues and all these issues are from one place (cache update).

lativ: I don't think #111892 is related. the issue explicitly states that the reporter didn't rename the folder. So it's
hardly an projectManager cache issue as the project folder stays the same. AFAIK all that is to be done in such case is
to return a different value from ProjectInformation.getDisplayName() and somehow persist this change (eg. in project.xml
for ant projects)

Fixed in trunk for bpel module:

/cvs/enterprise/bpel/project/src/org/netbeans/modules/bpel/project/BpelproProjectGenerator.java,v  <--  
BpelproProjectGenerator.java
new revision: 1.15; previous revision: 1.14

the issue 111892 was fixed
The "close 2 projects" problem not reproduced on (Build 20071011035158).

Verified in build 200710150000.