Revision as of 15:02, 18 April 2012 by Jrechtacek (Talk | contribs)


Review of Patching Process in NetBeans 7.1

Based on feedback of !NetCat72 community we realized several problems and possible confusions from users point of view while distributing patches and releasing minor releases of NetBeans simultaneously - tracked as Issue 211076.

Patching in NetBeans 7.1 from users point of view

First start of 7.1 IDE
  • Fresh install of NetBeans 7.1
  • An user can see a notification 1 update found

Update of Autoupdate Services found
  • The update contains an update of Autoupdate module

12 other updates found
  • After installation of update of Autoupdate and restart IDE, user can see notification that rest of updates is read for update
Content of updates

14 updates found
  • Fine. All updates are installed and s/he can start using IDE.
  • Create a Java Application. Because it's the fresh IDE, Java feature is still switched off. IDE activates Java feature.

==> IDE is semi-updated now. Platform is up-to-date but Java has not been updated yet.

  • S/he does coding, testing, whatever.
  • On the next round checking for updates (once a week as the default) another bunch of updated will be offered to user.
Update of Java feature

Status of Java feature
Subversion plugin was patched
  • An user would like know if Java feature was updated or not. Opens Plugins, switch to Installed tab and select Java feature but there no indication about the update.
  • After switch into Showing details view and mark e.g. Subversion plugin. In plugin description is a note about !NetBeans7.1PatchesInfo

New release is available
  • Notification of available upgrade IDE


  • Autoupdate doesn't update disabled modules
  • Missing a solid feedback about the patch what is being installed.
  • Missing a evident mark what release+patch is currently installed (e.g. NetBeans7.1 with Patch1 included)
  • Confusing installing updates in several steps
    • First step: Install update of Autoupdate
    • Seconds step: Other updates of active modules
    • Third steps later: Further updates of modules what became active recently

Possible solution

  • Reduce patching on showstoppers only and publish minor releases as upgrades (i.e. new bits with own installer)
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo