NetBeans Installer FAQ

Welcome to the FAQ page for the NetBeans installer! Here you can find answers to the most frequently asked questions about the NetBeans installer.

If you have a question, send it to NBI mailing list and we will answer it on this page! Click here to view the archive for this mailing list.

What information is needed for a successful bug report.

• File an issue through Issuezilla for the nbi component.
• Provide a description of what happened from the user's perspective.
• Describe the initial state of the target system (what components were installed).
• List the actions you have performed (list of components selected for installation, list of components selected for uninstallation, etc.)
• Is the bug reproducible in one installer session or it is required to run several sessions? (In the latter case provide item #3 data for each session)
• Attach log files for each session (usually located at ~/.nbi/log/*.log).
• Attach the local product registry file (usually located at ~/.nbi/registry.xml).

How to clean up the system from previous installations

• Delete the ~/.nbi directory (%USERPROFILE%\.nbi on Windows).
• Delete the installation directories of the components you have installed.
• Delete the desktop and start menu/applications shortcuts.
• On the Windows platform, delete all nbi* registry entries from the following registry keys:
  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and
  HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.

How to uninstall NetBeans in Mac OS X

• Go to the Finder and open the Applications window. Find the NetBeans executable you want to uninstall
• Control-click (or right-click) the executable and select "Show package contents". A new window opens that contains the uninstaller.
• Double-click the uninstaller icon and follow the instructions.

How to perform silent installation

• On the first system, run installer with --record <statefile> switch (e.g. --record state.xml) and install everything you need. After finishing installation state.xml file would be created
• Review and edit the statefile (it's an XML file, with, hopefully, pretty self-explaining format)
• On the other systems, run the installer again, supplying the statefile and specifying the silent mode, --silent --state <statefile> (e.g. --silent --state state.xml)
• Everything should be installed correctly after the instaler process finishes.

What other commandline options are there to automate the installation process?