cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

Bug 98894 - OpenProjects.PROPERTY_OPEN_PROJECTS fired with null old/newValue
: OpenProjects.PROPERTY_OPEN_PROJECTS fired with null old/newValue
Status: RESOLVED FIXED
: projects
Generic Infrastructure
: 6.0
: All All
: P3 (vote)
: 6.0
Assigned To:
:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2007-03-25 20:08 by
Modified: 2007-03-27 17:28 (History)
Issue Type: DEFECT
:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2007-03-25 20:08:56
[For module Project UI API]

The old and new value returned by PropertyChangeEvent for property 
PROPERTY_OPEN_PROJECTS are null.

Workaround is for client code to cache the array of open projects returned by:

public Project[] getOpenProjects()

and then call the same API again in response to the PropertyChangeEvent and 
compute the diffs to detect opened and/or closed projects.

This is very inefficient.
------- Comment #1 From 2007-03-25 21:32:57 -------
While you're at it, could fix issue #64397.
------- Comment #2 From 2007-03-26 12:05:31 -------
done. values now contain array of projects (as the getter does).



IDE: [3/26/07 1:05 PM] Committing started
Checking in
projectui/test/unit/src/org/netbeans/modules/project/ui/OpenProjectsTrampolineImplTest.java;
/cvs/projects/projectui/test/unit/src/org/netbeans/modules/project/ui/OpenProjectsTrampolineImplTest.java,v
 <--  OpenProjectsTrampolineImplTest.java
new revision: 1.6; previous revision: 1.5
done
Checking in
projectui/test/unit/src/org/netbeans/modules/project/ui/OpenProjectListTest.java;
/cvs/projects/projectui/test/unit/src/org/netbeans/modules/project/ui/OpenProjectListTest.java,v
 <--  OpenProjectListTest.java
new revision: 1.12; previous revision: 1.11
done
Checking in
projectui/src/org/netbeans/modules/project/ui/OpenProjectsTrampolineImpl.java;
/cvs/projects/projectui/src/org/netbeans/modules/project/ui/OpenProjectsTrampolineImpl.java,v
 <--  OpenProjectsTrampolineImpl.java
new revision: 1.10; previous revision: 1.9
done
Checking in projectui/src/org/netbeans/modules/project/ui/OpenProjectList.java;
/cvs/projects/projectui/src/org/netbeans/modules/project/ui/OpenProjectList.java,v
 <--  OpenProjectList.java
new revision: 1.66; previous revision: 1.65
done
Checking in
projectuiapi/src/org/netbeans/modules/project/uiapi/OpenProjectsTrampoline.java;
/cvs/projects/projectuiapi/src/org/netbeans/modules/project/uiapi/OpenProjectsTrampoline.java,v
 <--  OpenProjectsTrampoline.java
new revision: 1.6; previous revision: 1.5
done
Checking in projectuiapi/src/org/netbeans/api/project/ui/OpenProjects.java;
/cvs/projects/projectuiapi/src/org/netbeans/api/project/ui/OpenProjects.java,v 
<--  OpenProjects.java
new revision: 1.10; previous revision: 1.9
done
IDE: [3/26/07 1:05 PM] Committing finished
------- Comment #3 From 2007-03-27 15:51:27 -------
I blogged about this fix here:

http://blogs.sun.com/scblog/entry/monitoring_opening_and_closing_og

I received a commenty asking whether this will be fixed in some hotfix release?

Comment:

...Is there a plan, for releasing netbeans fixes as hotfixes/binary patches ? 
I see no reason in doing so, especially considering that what is affected at 
most is one or 2 classes. So why should one need to get unstable CVS head 
branch for fixes ? Shouldn't netbeans have a update support that can update 
core features for stuff like bug fixes/security updates etc ? 

Posted by gumnaam

Is there a plan to fix this bug in NetBeans 5.5 hot fix or NetBeans 5.5.1?
------- Comment #4 From 2007-03-27 17:28:20 -------
P3 bugs are generally not backported. Some P1-P2 bugs are.