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.
The issue was raised in the forum: http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=787006 > When I went to do the Update Center this morning, I noticed an update > from the NetBeans Hotfix Update Center labeled "Core" (with no > description). What is this? Do I need it? The client should provide more info about the hotfixes. Perhaps clicking the 'More' button should provide detailed info on the hotfixes.
Issues included in the patch are marked with keyword 55_PATCH3. Please see http://www.netbeans.org/issues/describekeywords.cgi and also http://www.netbeans.org/issues/buglist.cgi?keywords=55_PATCH3 . At least this info should be in the short description of every patch module. (Note: The short description is visible in the bottom text area in the Update Center Wizard dialog when a user Selects Modules to Install.)
I filed issue 101054 for making the UI in the plugin manager better for displaying hot fix info.
Some suggestions: > http://www.netbeans.org/issues/buglist.cgi?keywords=55_PATCH3 . Since the hotfixes are cumulative, we can use the more generic query: http://www.netbeans.org/issues/buglist.cgi?keywords=55_PATCH3%2C55_PATCH2%2C55_PATHC1&keywords_type=anytokens Also consider if 55_HOTFIX3 would be a better keyword than 55_PATCH3. > At least this info should be in the short description of every patch module. While making the info a part of short description is certainly more user friendly, it also requires modification of each module. Instead, please consider assigning a URL to the 'More' button. For 6.0, a more formal method can be considered, which can be discussed at issue 101054. For 55 and 551, the 'More' button for hotfixes can point to a page on our wiki site which can include the link to a query based on keywords as mentioned above. (Of course, the more button can directly point to the query itself. But pointing it to a dedicated wiki page would allow us to add more info like any special instructions etc, if such info is needed later). Of course, the wiki page can simply list the issue ids directly, in which case the keywords may not be needed.
Some suggestions on the wiki page: - Create a toplevel category 'Sustaining' as in http://wiki.netbeans.org/wiki/Sustaining (in parallel to Development and QE). For now, there may not be a need to add a direct link to this sustaining page from the wiki's main page; such a link should probably added after discussions with the community. - The main sustaining page "http://wiki.netbeans.org/wiki/view/Sustaining" can initially be based on "http://developers.sun.com/jsenterprise/downloads/patches/" . - The individual readmes for hotfixes can be modelled on sunsolve readme as in: http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&max=50&language=en&queryKey5=121045&toDocument=yes There are several sections in sunsolve format that are not needed for NetBeans hotfixes and these can be removed. Similarly of course new sections can be added that are relevant for NB hotfixes. - Right now there is no correlation between nbms and bugs fixed. This can be solved by associating nbms with their module short description and then by grouping issues fixed under module short descriptions.
The wiki page http://wiki.netbeans.org/wiki/view/NetBeans5.5PatchesInfo has been created for tracking all NetBeans 5.5 bugfixes. The similar page will be created for next NetBeans releases and its URL will be assigned to the 'More' button in Update Center Wizard.
Checking in projectized.xml; /cvs/nbbuild/templates/projectized.xml,v <-- projectized.xml new revision: 1.58.10.1.2.8.26.1; previous revision: 1.58.10.1.2.8 done
The issue has been ported into release551_fixes branch. Checking in projectized.xml; /cvs/nbbuild/templates/projectized.xml,v <-- projectized.xml new revision: 1.58.10.1.2.8.40.1; previous revision: 1.58.10.1.2.8 done
Verified.
The additional change of "nbm.homepage" value in "project.properties" files are needed for UML modules because they overrides the value of "nbm.homepage" in "nbbuild/templates/projectized.xml". Checking in core/nbproject/project.properties; /cvs/uml/core/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.13.8.1; previous revision: 1.1.2.13 done Checking in ideintegration/nbproject/project.properties; /cvs/uml/ideintegration/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in projectui/nbproject/project.properties; /cvs/uml/projectui/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in webreport/nbproject/project.properties; /cvs/uml/webreport/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in tomsawyer/nbproject/project.properties; /cvs/uml/tomsawyer/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.6.12.1; previous revision: 1.1.2.6 done Checking in documentation/nbproject/project.properties; /cvs/uml/documentation/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in doorsrequirements/nbproject/project.properties; /cvs/uml/doorsrequirements/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.5.10.1; previous revision: 1.1.2.5 done Checking in xmlrequirements/nbproject/project.properties; /cvs/uml/xmlrequirements/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in propertysupport/nbproject/project.properties; /cvs/uml/propertysupport/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in bankappsample/nbproject/project.properties; /cvs/uml/bankappsample/nbproject/Attic/project.properties,v <-- project.properties new revision: 1.1.2.2; previous revision: 1.1.2.1 done Checking in modelingpalette/nbproject/project.properties; /cvs/uml/modelingpalette/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in kit/nbproject/project.properties; /cvs/uml/kit/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.1.10.1; previous revision: 1.1.2.1 done Checking in java5parser/nbproject/project.properties; /cvs/uml/java5parser/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.9.8.1; previous revision: 1.1.2.9 done Checking in antlr-2-7-2/nbproject/project.properties; /cvs/uml/antlr-2-7-2/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.6.12.1; previous revision: 1.1.2.6 done Checking in requirements/nbproject/project.properties; /cvs/uml/requirements/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in drawingareacontrol/nbproject/project.properties; /cvs/uml/drawingareacontrol/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.8.8.1; previous revision: 1.1.2.8 done Checking in designpattern/nbproject/project.properties; /cvs/uml/designpattern/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.5.10.1; previous revision: 1.1.2.5 done
Checking in project.properties; /cvs/uml/dom4jdependencies/nbproject/project.properties,v <-- project.properties new revision: 1.1.2.6.12.1; previous revision: 1.1.2.6 done
Closing the issue as both 55 and 551 hotfix and uml nbms point to the relevant pages on wiki.