This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 142928 - First project created using NewProjectWizardOperator not opened in project window
Summary: First project created using NewProjectWizardOperator not opened in project wi...
Status: RESOLVED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Dialogs&Wizards (show other bugs)
Version: 6.x
Hardware: All Mac OS X
: P2 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords: TEST
Depends on:
Blocks: 140947
  Show dependency tree
 
Reported: 2008-08-05 14:15 UTC by Ivan Sidorkin
Modified: 2009-11-02 11:03 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Sidorkin 2008-08-05 14:15:04 UTC
First project created using NewProjectWizardOperator not opened in project window
next projects opened fine.

this issue block using auto tests on MacOS
Comment 1 Alexandre Iline 2008-08-05 15:22:15 UTC
Is there a test case I could use to see the problem?
Comment 2 Ivan Sidorkin 2008-08-05 15:26:33 UTC
run
ant -Dtest.config=ruby test
in ide.kit
Comment 3 Alexandre Iline 2008-08-06 14:57:19 UTC
Here is a workaround.
NewProjectWizardOperator.invoke().cancel();

As the priority is coming from the blocked P1 against commit validation and, with this workaround it will be fixed, I decrease the priority.

Comment 4 Tomas Zezula 2008-09-08 15:16:27 UTC
Moving back to P1, the MemoryValidationTest which is part of commit validation fails on Mac.
Comment 5 Alexandre Iline 2008-10-31 14:00:56 UTC
I have narrowed it to a race condition in TemplateWizard. 

A comment in instantiateImpl method says:
        // here can return newObjects because instantiateNewObjects() was called
        // from WizardDescriptor before close dialog (on Finish)

Well, on mac it is not allways true. I did this change:
$ hg diff openide.loaders/src/org/openide/loaders/TemplateWizard.java
diff -r 950f7af22983 openide.loaders/src/org/openide/loaders/TemplateWizard.java
--- a/openide.loaders/src/org/openide/loaders/TemplateWizard.java       Fri Oct 31 15:41:34 2008 +0300
+++ b/openide.loaders/src/org/openide/loaders/TemplateWizard.java       Fri Oct 31 15:59:29 2008 +0300
@@ -395,6 +395,7 @@ public class TemplateWizard extends Wiza
     }

     Set<DataObject> instantiateNewObjects (ProgressHandle handle) throws IOException {
+        System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! instantiateNewObjects called");
         progressHandle = handle;
         try {
             // #17341. The problem is handling ESC -> value is not
@@ -499,6 +500,7 @@ public class TemplateWizard extends Wiza

         // here can return newObjects because instantiateNewObjects() was called
         // from WizardDescriptor before close dialog (on Finish)
+        System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! instantiateImpl exits");
         return newObjects;
     }

and the output confirms my findings.

Comment 6 Alexandre Iline 2008-10-31 14:02:30 UTC
To reproduce, simple run org.netbeans.jellytools.NewProjectWizardOperatorTest test from IDE.
Comment 7 Jaroslav Tulach 2008-10-31 17:29:38 UTC
Jirko, I guess this is your code. Will you investigate the problem?

changeset:   bb276c9cffeb
user:        jrechtacek@netbeans.org
date:        Sun Aug 06 15:58:35 2006 +0000
summary:     #58889: Enhance wizard framework to display progress indication on Finish
Comment 8 Jiri Rechtacek 2008-10-31 17:41:49 UTC
> Jirko, I guess this is your code. Will you investigate the problem?
> 
> changeset:   bb276c9cffeb
> user:        jrechtacek@netbeans.org
> date:        Sun Aug 06 15:58:35 2006 +0000
Jardo, you are saying these test failing since Aug 06 15:58:35 2006 +0000? I don't think so. Assigning back.
> summary:     #58889: Enhance wizard framework to display progress indication on Finish

Ivan, what means current version? NB6.1? NB6.5? NB7.0? Thanks
Comment 9 Jaroslav Tulach 2008-10-31 18:20:18 UTC
No, I am saying that this is work for owner of dialogs API. The TemplateWizard has always been maintained by that 
module owner.
Comment 10 Jiri Rechtacek 2008-10-31 18:32:25 UTC
Okay, I was confusing by your comment. Do you know from when there is this problem? I doubt I did some changes there for
ages.
Comment 11 Alexandre Iline 2008-11-01 06:49:33 UTC
I do not know for how long this is around, actually.

My be it was there for a long time and manifested itself just recently by tests on Mac OS only. The platform did not 
have the highest priority, honestly.

As you can see it the issue is entered in Aug. I remember it was narrowed down from commit validation at that moment. 
I am not sure for how long commit validation was failing because of that.
Comment 12 Marian Mirilovic 2008-11-02 09:32:17 UTC
I do not think it has to be solved for NB 6.5. Ivan, do you agree ?
Comment 13 Ivan Sidorkin 2008-11-05 16:36:17 UTC
yes, it is not necessary to fix it in 6.5
Comment 14 Jiri Rechtacek 2008-11-06 10:38:01 UTC
There is the known workaround NewProjectWizardOperator.invoke().close(); which is performing for ages in
IDEValidation.testMainMenu(). The original problem is some race condition between WizardDescriptor and TemplateWizard
callback calling. But no one reported such problem in IDE, it's visual test specific, moreover Mac specific (on other
platforms are tests passing). I decreasing the priority to P2.
Comment 15 Alexandre Iline 2008-11-06 11:19:32 UTC
The workaround is mentioned in the issue comments already - we know about it.

P2 is fine.
Comment 16 Jiri Rechtacek 2008-12-10 09:59:38 UTC
It's the known bug, which doesn't affect IDE usability to end-user's.  I guess its fix will destabilize TemplateWizard
code and probably make some regressions. I don't plan to fix it sometime presently.
Comment 17 Quality Engineering 2009-11-02 11:03:51 UTC
NetBeans.org Migration: changing resolution from LATER to WONTFIX