NetBeans IDE is a modular, standards-based integrated development environment (IDE),
written in the Java programming language. The NetBeans project consists of an open
source IDE written in the Java programming language and an application
platform, which can be used as a generic framework to build any kind of application.
NetBeans IDE 6.1 is a significant update to NetBeans IDE 6.0 and
includes the following changes:
JavaScript support.
Spring Framework Support.
New MySQL support in Database Explorer. This feature allows you to register a MySQL Server, view databases, view, create, and delete databases, easily create and open connections to these databases, and to launch the administration tool for MySQL. This also allows you to easily create NetBeans sample databases so that following tutorials, blogs, and so on is significantly easier.
Support for Java Beans. You can now view Java Bean patterns in the Navigator and BeanInfo Editor.
JSF CRUD Generator. With this feature, you can generate a JavaServer Faces CRUD application from JPA entity classes.
Javadoc Code Completion. Editing of javadoc comments is more convenient with code completion.
Shareability of projects. This new feature in Java SE, Java Web, and all Java EE project types allows you to create projects that share definitions of libraries. That in turn allows you to create self-contained projects or sets of projects that can easily be built from the command line, on continuous integration servers, and by users of other IDEs without problems.
Existing infrastructure has been enhanced to support window transparency (on platforms that provide it).
Javadoc and sources association. Now any JAR item on the project classpath can be associated with its Javadoc and sources too.
Inspect Members and Hierarchy Windows. Inspect Members and Hierarchy actions now work when the caret in the Java Editor is on a Java class for which there is no source available.
On Demand Binding Attribute for Visual Web JSF projects.
Axis2 support for web services.
SOAP UI integration for Web Service testing and monitoring.
NetBeans IDE 6.1 supports the following technologies and has been tested with the following application servers.
If you plan to use versions of JBoss, WebLogic, or Struts other than those explicitly listed, please note that you may encounter unpredictable IDE
behavior as a result of the technologies being external interfaces which the project team has little or no control over.
Supported technologies:
Enterprise JavaBeans (EJB) 3.0
JAX-WS 2.1
Java Persistence (JSR-220)
JavaServer Faces 1.2 (JSR-127)
Java Servlet 2.5
JavaServer Pages (JSP) 2.1
Struts 1.2.9
Java API for XML-based Remote Procedure Calls (JAX-RPC) 1.6
Java APIs for XML Registries (JAXR) 1.0
Java API for XML Processing (JAXP) 1.4
Java Architecture for XML Binding (JAXB) 2.1
JavaServer Pages Standard Tag Library (JSTL) 1.1
Tested application servers:
Sun Java System Application Server 9.0 (GlassFish V1)
Sun Java System Application Server 9.1 (GlassFish V2)
Sun Java System Application Server PE 8.2
Tomcat 5.5
Tomcat 6.0
JBoss 4.0.4
WebSphere 6.0
Websphere 6.1
WebLogic 9.2
WebLogic 10
Note: If you are using the GlassFish application server, it is recommended that
you run GlassFish V2 in order to work with NetBeans IDE 6.1.
System Requirements
NetBeans IDE runs on operating systems that support the Java VM (Virtual Machine) and has been tested on the platforms listed below.
Note: The IDE's minimum screen resolution is 1024x768 pixels.
Supported Operating Systems
Minimum Hardware Configurations
Microsoft Windows XP Professional SP2:
Processor: 800MHz Intel Pentium III or equivalent
Memory: 512 MB
Disk space: 750 MB of free disk space
Microsoft Windows Vista:
Processor: 800MHz Intel Pentium III or equivalent
Memory: 512 MB
Disk space: 750 MB of free disk space
Ubuntu 7.x:
Processor: 800MHz Intel Pentium III or equivalent
Memory: 512 MB
Disk space: 650 MB of free disk space
Red Hat EL 4:
Processor: 800 MHz Intel Pentium III or equivalent
NetBeans IDE is also known to run on the following platforms:
Java Desktop System 2
Microsoft Windows 2000 Professional SP4
Mac OS X 10.4.5 Intel
Various other Linux distributions, such as Red Hat Enterprise Linux
Note: While the above system requirements apply to most configurations
of the IDE, some areas of NetBeans Web and Java EE support are particularly
demanding on system resources, especially when used in combination with
various application servers. For best results when developing Web and Java EE applications,
make sure that your system meets at least the recommended system requirements.
Required Software
NetBeans IDE runs on the J2SE (Java SE Development Kit) JDK 5.0 Update 14 and higher (including JDK 6.0), which consists of the Java Runtime
Environment plus developer tools for compiling, debugging, and running applications written in the Java language.
You can download the JDK for your platform from one of the sites listed
below:
When you first run the IDE, you can import a subset of the settings
you used in previous versions of NetBeans IDE. If you choose not to import settings from a previous
release, the IDE opens using the default settings.
Note: The IDE only recognizes previous installations where
the user directory resides in the default location. It does not recognize
installations where you have specified a user directory using the --userdir
switch. If you would like to import settings from an IDE that the installer
does not recognize, download an archive version of the IDE instead of using the
installer.
Note: If you edit the Project Properties in NetBeans IDE 6.1
for a project that was created
in NetBeans IDE 4.1 or earlier, the project will no longer
work in the earlier NetBeans IDE versions.
There have been changes made to the database functionality in NetBeans 6.1. They are as follows:
Java DB Database Server moved to Services window. In previous versions of the IDE, the Java DB Database Server was administered from Tools in the main menu. In NetBeans IDE 6.1, creating, deleting, and other database administration is done using the Java DB node in the Services window.
Visual Query Editor. The Visual Query Editor has been removed from the Database Explorer and is now available only as part of the visual web framework.
Additional MySQL Support added. NetBeans IDE 6.1 features more support for MySQL. Using the MySQL node in the Services window, you can now start and stop a MySQL server, as well as access the MySQL administration tool. It is also easier to manipulate MySQL databases in NetBeans IDE 6.1.
Upgraded Drivers. PostgreSQL and MySQL drivers included in NeBeans IDE have been updated. The PostgreSQL driver version is now 8.3-603; the MySQL driver version is 5.1.5.
SQL Editor: New 'Delimiter' Directive. The new 'delimiter' directive in the SQL editor allows you to execute stored procedures and triggers and other multi-statement blocks. In the past this didn't work because the SQL Editor would incorrectly split the procedure into multiple semicolon-delimited statements and try to execute them separately. You can avoid this problem by using the 'delimiter' directive to set the delimiter to something other than semicolon. For example:
delimiter ??
create procedure test()
begin
declare x tinyint;
select count(*) from person into x;
if x = 2
then
select * from trip;
end if;
end??
delimiter ;
call test();
Tested Drivers
NetBeans IDE 6.1 has been tested with the following databases and drivers.
Description: On Solaris and Linux platforms, if the network connection is lost, installation hangs when the installer is searching for a compatible JDK in network directories.
Workaround: Restore the network connection and proceed with the installation.
Description: On Macintosh platforms, if you are using only JDK 6.0 you may experience some installation problems because this JDK version is not of FCS quality. The preferred JDK for the Mac OS is 1.5.0_07.
Description: Installation stops with error during execution of the unpack200 command. This error can be caused by the Logitech Process Monitor (Webcam Effects Helper) application.
Workaround: If you have Logitech Process Monitor (Webcam Effects Helper) application (LVPrcSrv.exe) that is running on your system, switch it off before installation or uninstall.
On MacOS the installer freezes during installation when the unpack200 command is executed.
Description: The installer freezes during installation and the following error is reported:
Unable to find unpack200
Workaround: Make a symlink named unpack200 that points to /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/bin/unpack200. Note that the symlink must be placed in a folder in the unpack200 path. For example, in the path shown above, the bin folder is a good location.
Issue #122030, Issue #130368: On Fedora 8 and
Ubuntu 8.04 alpha 6, installation fails when JDK 7 is used.
Description: On Fedora 8 and Ubuntu 8.04 alpha 6, installation of GlassFish V2 fails when JDK 7 is used (JDK7 IcedTea 64-Bit Server VM).
Workaround: For these platforms, use JDK 5 or JDK 6.
The NetBeans IDE 6.1 Download page can be displayed in the language
selected from the Choose Page Language drop-down list.
Description: The Download page is displayed in the language which is
specified as default for the used browser. If you are using a non-localized
browser, it will be displayed in English. To view the Download page in
Chinese, Japanese, or Brazilian Portuguese, select the relevant language
from the Choose Page Language drop-down list at the top of the Download page.
Workaround: The localized Chinese, Japanese, and Brazilian Portuguese versions of the Firefox browser
allow opening a localized Download page. To view the Download page in Chinese, Japanese, or Brazilian Portuguese, select the relevant language from the Choose Page Language drop-down list at the top of the Download page.
The NetBeans IDE 6.1 installation wizard does not start properly (hangs). After the user stops the installation process manually, and the installer reports that another installer instance is running.
Description: On Windows, when Java6 is used by default and large zip files are stored on the desktop, the installation wizard does not start properly (hangs). After the user stops the installation process manually, and the installer reports that another installer instance is running.
Workaround: Before the installation, remove all big zip files from the desktop
The unresolved issues for this release are as follows:
Difficulties starting the IDE (Solaris x86 and Dual-Core Opteron).
Description: On certain Solaris x86 and Dual Core Opteron configurations,
you may encounter problems starting the IDE due to a JDK bug with loading GTK look&feel libraries.
Workaround: If you encounter this behavior, specify the following command line option:
-laf javax.swing.plaf.metal.MetalLookAndFeel
Characters do not display properly in some Asian locales.
Description: When running the IDE with some Asian locales on Ubuntu and some other Linux distributions,
the IDE's screen text may become unreadable. On certain Linux distributions multi-byte characters may display as
a rectangle due to JDK font setting issues.
Workaround: Because there is no known workaround for this issue, it is recommended to use
an alternative Linux distribution if you must use a locale subject to this behavior.
Issue #64840:
Network communication broken on Linux with IPv6 enabled.
Description: Network communication broken on Linux with IPv6 enabled,
preventing the IDE from connecting to bundled servers,
Auto Update, etc.
Workaround: If this happens, run the IDE using the
-J-Djava.net.preferIPv4Stack=true' switch.
Alternatively, disable IPv6 (in /etc/modules.conf
or /etc/modprobe.conf).
Issue #62919:
Profiled application can crash when taking a memory snapshot.
Description:When profiling an application, the profiled application
may crash when you attempt to take a memory snapshot.
Workaround: Start the application you want to profile with the -Xnoclassgc switch.
Issue #110074:
Editor periodically freezes on Solaris.
Description: When running the IDE on Solaris with
JDK 6, 6u1 or 6u2, threads may become blocked for a long time and
cause the editor to be unresponsive.
Workaround: Upgrade your JDK 6 installation to Update 3 or newer.
Issue #88776:
Profiled application can crash when profiling using dynamic attach mode.
Description:When running on JDK 1.6,
profiling an application with dynamic attach mode can lead to the profiled application crashing.
Workaround: Start the application you want to profile with the -Xshare:off switch.
JDK 6 Issue #6389282:
Java applications created from the Java Desktop Application project template might not run under Chinese and
Japanese on Linux when using JDK 6.
Description: Java applications created from the
Java Desktop Application project template might not be able to be run in
Japanese and Chinese Linux locales with JDK 6 installed.
Workaround: Use JDK 5.0 or run projects from English locale.
Issue #119617:
Cursor lost in editor and cannot type using keyboard
Description: It can sometimes occur that after using a hint in the editor window
that the insertion point in the editor disappears and you cannot type using the keyboard.
This has mostly been reported on Mac OS X 10.4, but there have been some reports on some versions of Ubuntu.
Workaround: Use the mouse to open and then close a dialog window (for example, a properties dialog).
This returns the focus to the editor and the insertion point and keyboard will work as normal.
Issue #119567:
Desktop database application project does not run if non-ASCII is in the name of the project or the path to that project.
Description: The cause is in the current toplink libraries used in the IDE.
An issue on toplink library has been filed on it. This Glassfish issue has been fixed for Glassfish v2.1. However, NetBeans 6.1 supports glassfish v2 u2, and the fix is not in this version of Glassfish.
Workaround: Use only ASCII characters in the name of a desktop database application project or the path to that project.
Issue #118174 and other related issues: I18N - Javadoc not found on Solaris, maybe other platforms, in certain cases using the Firefox
web brower
Description: When using Firefox on Solaris, and sometimes on Mac OS and Windows, if multibyte or non-ascii characters are used in project name or path, and if the project encoding property is not set to utf-8 (which means these paths are in that encoding), the generated javadoc is not found or shown.
For example: In the case of a project that has euc-jp as its project encoding property on Solaris, and has project name or path using Japanese characters of that encoding, the javadoc won't be found and an error message
is displayed in Firefox.
The problem is that part of the URL is UTF-8 and part is EUC-JP; the
javadoc tool stores the URL in the encoding it
generates for the web page, but the correct way is to generate the text in
requested encoding (in this case EUC-JP) and URLs in UTF-8.
Workaround: Avoid using multibyte in the name of the project or the path to the project.
Issue #130357: I18N - Mac OS won't generate javadoc if project name or path has multibyte
Description: The javadoc task while creating the temporary parameter file is written in default OS encoding which is MacRoman.
This appears to be a Mac OS situation where the BSD and Mach parts (system & kernel calls) accept parameters in UTF-8,
but OS and HFS promote themselves as MacRoman.
Workaround: Avoid using multibyte in the name of the project or the path to the project.
Issue #130311: On Mac OS, some messages or strings in another language or character set are not shown in output window correctly
Description: For example, on Mac OS X 10.4. when using System.out.println in the Java code,the strings containing Japanese characters display correctly in the source code, but are displayed as question marks in the output window.
Workaround: There is no workaround at this time.
Issue #130245: I18N - Mac OS: A Mercurial (hg) repository cannot be created from a project if multibyte is in path to the project on a Mac using 10.4.x.
Description: An error message is displayed in the Output window or Terminal after trying to create the repository.
Note: This problem does not occur on Mac 10.5 with Mercurial 1.0 or
Mercurial 0.9.5. The problem occurs on Mac 10.4 with Mercurial 0.9.5 (Mercurial 1.0 is currently not available for Mac 10.4).
Workaround: Create A Mercurial repository from command line by using the command
hg init <DirectoryName>.
Issue #133893: Refactoring(Rename) fails with ClassCastException
Description: While refactoring (removing, renaming, etc.) a Java class, the refactoring dialog displays the following error: "Module Spring Beans threw java.lang.ClassCastException: org.netbeans.editor.ext.ExtSyntaxSupport". This happens especially in a web project which was extended by the Spring Web MVC framework.
Workaround: Right-click the project node in the Projects view and click Properties. In the Project Properties dialog, select the Spring Framework category. In the Configuration Files tab, remove the web/WEB-INF/jsp/index.jsp file and click OK.
The unresolved Web and Java EE issues for this release are as follows:
Visual Web JSF Backwards Compatibility Kit
Description: The Visual Web JSF Backwards Compatibility kit provides supplemental libraries that are required by the Visual Web designer to support projects that are based on J2SE 1.4 or J2EE 1.4. These libraries are not open source and are therefore distributed as a separate NetBeans plugin. The kit will install the following libraries that are required for J2EE 1.4 projects:
Description: Blue Prints Ajax Sample components are not supported in this release because they are based on a old version of Dojo that is no longer compatible with later versions. Woodstock components bundled in NetBeans depends on more recent versions of Dojo APIs for client side rendering. For most of the widely used BP Ajax components (supported in NetBeans 5.5), there is equivalent functionality available from Project woodstock as listed below.
Auto Complete - This blog (http://blogs.sun.com/dmitry/entry/creating_autocomplete_entry_field_with ) describes how to achieve similar functionality with components from Project Woodstock library.
Pop up Calendar - Project Woodstock includes a Calendar component.
Select Value field - Use auto complete instead which has similar functionality but different UI.
Progress Bar - Project Woodstock includes a Progress Bar component.
Google Map - Planned for future.
Rating Component - Planned for future.
RichText Editor - Not supported.
Issue #113888: Woodstock themes are incompatible with migration of projects from NetBeans IDE 5.5/5.5.1 to NetBeans 6.1.
This issue is related to Issue #99063, Missing Body Element switching to new Woodstock theme.
Description: Projects with custom themes migrated to NetBeans IDE 6.1 will produce Missing Body Element errors.
Workaround: Manually switch to the default theme before migrating.
Custom themes will not work and will need to be rebuilt.
Issue 94193: Not possible to edit bean properties
in the Outline window or through source packages in the Projects window.
Description: In NetBeans IDE 6.1, the Add Menu item is disabled in the Navigator window and there is
no functionality for editing the properties through source packages.
Workaround:
Double click SessionBean1 (or other java file) to open the bean in the Java editor.
Manually add the property, such as private String CustomerId;.
Right click on the property and choose Generate Code.
From the Generate popup menu, select Getters and Setters.
In the Generate Getters And Setters dialog for SessionBean1, select your property and press OK.
Public Getter and Setter methods are inserted after your property.
Issue #95022: Resizing of text field and other components does not work.
Description: Due to a change in Woodstock components, resize handles have been removed from the following Woodstock components: TextField, Text Area,Password Field, Drop Down and List Box. This issue impacts especially projects imported from Java Studio Creator and NetBeans Visual Web Pack 5.5/5.5.1. Resized components may look different from how they looked in previous releases.
Workaround: For TextField and Text Area components, use the columns and rows attributes, respectively. Drop Down and List Box have been enhanced to include a new width property.
When displayed in IE7, all button components may be rendered with an incorrect width.
Description: When a button is placed using absolute positioning, its width is incorrect. For example,
when NetBeans IDE 6.1 uses absolute positioning to place components in Grid Layout Mode, this problem may occur.
IE7 expects a value to be specified for the width of buttons. If a width attribute is not specified, the width is set
to width:auto, which results in the button's width being set to the entire available width of the button's container element.
For example, if the button style has left=130px then the button will start at 130px left and will expand to the width of
the <body> element.
Workaround: There are several different ways to solve this issue in NetBeans:
Specify the width property for the button, or resize the button in the IDE to make the IDE assign a width to the button.
In the IDE, drop the button into a Group Panel component to put the button inside a span tag. In this case there is no need to set the positioning as the
IDE sets the positioning for the Group Panel component. For example, the JSP code of a Button inside a Group Panel component may look like this:
Issue #106299: faces-config.xml of Visual Web JSF projects no longer contains the locale section, as in previous versions.
Description: faces-config.xml used to have the commented section listing how to indicate other locales, with some lines for certain locales as an example. Users must now add these line manually, making sure the name of the locales of interest are in the supported locales
section.
Workaround: Manually add the desired locale to the locale section of the faces.config.xml file. Here is an example of how the code should appear:
Issue #125965: Null Pointer Exception on drag and drop after closing a Visual Web project close.
Description: When working with two Visual Web JSF projects, and when closing the second project and returning
to the first, may yield an Null Pointer Exception for the first drag and drop.
Workaround: Press refresh in designer and continue working.
If this does not help, it is necessary to restart the IDE.
NetBeans 6.1 Web Services enables you to develop SOAP and RESTful services and clients. JAX-WS (Metro), REST (Jersey), Axis2, and JAX-RPC architectures are supported.
The unresolved Web Services issues for this release are as follows:
Issue #129077: Dragging and Dropping Facebook Service to a Servlet or Resource Class
Description: There are compilation issues with /src/org.netbeans.saas.facebook.FacebookService.java and /src/org.netbeans.saas.facebook.FacebookService.java. In addition, the Callback servlet class is missing, and so is its registration in web.xml.
End to End support not enabled with NetBeans 6.1 Mobility installation.
Description: Mobile applications can not be connected to an enterprise using the Mobility distribution of NetBeans 6.1.
Workaround: Install the Mobility End to End plugin.
In the IDE's main menu go to Tools > Plugins.
In the Plugins dialog click the Available Plugins tab.
In the Name column of the Available Plugins, find Mobility End to End.
Check the box next to Mobility End to End and click Install.
The NetBeans IDE Installer dialog shows the plugins about to be installed. If additional plugins are necessary, the IDE selects them automatically. Click Next.
A license agreement may appear next. To enable End to End functionality, accept the license agreement and click Install.
Note: You can also enable End to End functionality by installing the full distribution of NetBeans 6.1.
The Mobility pack will not run if a directory name, path to the
installation directory, or user directory contain non-ASCII characters.
Description: The Sun Java Wireless Toolkit does not support non-ASCII
characters in project paths.
Workaround: Make sure that your user directory does not contain
non-ASCII characters. If it does, change the IDE's default
user directory.
JDK 6 Issue #6389282: Chinese and Japanese Linux locales with JDK 6 may fail to run projects.
Description: Mobile application projects created in NetBeans can not be run in Japanese and Chinese Linux locales with JDK 6 installed.
Workaround: Use JDK 5.0 or run projects from English locale.
NetBeans 6.1 UML lets you explore and evaluate the UML functionality in the IDE. We encourage you to get involved and give us feedback by logging any issues you encounter in the Issue Tracking system at http://www.netbeans.org/community/issues.html.
Note: NetBeans 6.1 UML is currently not supported on the Macintosh OS X platform. UML is available for the Macintosh OS X platform via the NetBeans Plugin Manager. Please see the NetBeans wiki for UML Mac issues, http://wiki.netbeans.org/wiki/view/UMLMacIssues to get more information about the known Macintosh OS X issues and workarounds.
This NetBeans SOA 6.1 release lets you explore and evaluate new functionality in the IDE. We encourage you to get involved and give us feedback by logging any issues you encounter in the Issue Tracking system at http://www.netbeans.org/community/issues.html.
The unresolved SOA issues for this release are as follows:
Issue #114171: WSDL files manually edited by CASA throw Null Pointer Exception in the build.xml output.
Description: CASA does not support user editing of its generated files, and provides no warning when a user does so.
Workaround: Do not edit CASA-generated WSDL files. Manual editing of WSDL file is not supported and will cause unexpected results.
Issue #84622: IDE does not roll back the retrieval of the WSDL file(s) after you cancel the PartnerLink dialog.
Description: If you cancel the PartnerLink dialog that appears when you drag a WSDL file or a Web Service node from a NetBeans project onto a diagram, the IDE does not roll back the retrieval of the WSDL files(s).
Workaround: If these files are not needed by the project, simply delete them manually from the Projects window, as you would delete any other project resource.
Issue #112344: Drag and Drop in the tree view of XML schema editor may throw exceptions.
Workaround: Use JDK 1.6.0_02 or later.
Issue #96237: The XSLT Designer does not support messages defined on complex, simple, or built-in types.
Description: In this release, the XSLT Designer does not support messages declared in WSDL using the type="..." attribute. Only the declarations with the element="..." attribute are supported.
Issue #132274: WSDL from database wizard throws an exception and creates
incorrect wsdl file on Solaris in Japanese locale (euc-jp) .
Description: Sometimes, on completion of using File > New WSDL from database wizard, there is an exception and an incorrect wsdl file with an
empty source view is created. This happens when running if Solaris ja (euc-jp) locale;
It might happen in a similar locale on Linux or MacOS and might even happen using other Unix non-utf8 locales on Solaris. It does not happen on Windows. It also does not happen when running in solaris ja utf-8 or other utf-8 locales.
Workaround: Running NetBeans in utf-8 ja or other utf-8 locales can partially solve the problem, but the means user will need to change existing files that were created or imported in euc-jp encoding to use
utf-8 encoding. Otherwise, the user might not be able to see properly some characters.
For example, the issue does not happen if user is running NetBeans while in the Solaris ja_JP.UTF-8 locale.
Issue #133136: The IDE is unresponsive for a long period of time after formatting the xml schema code.
Description: After performing format of a large xml schema file, the next action in the IDE will cause it to hang for a long time. It can take more than 10 minutes for the IDE to come back to the normal state.
Workaround: Usually you just have to wait.
Issue #132544 : Deployment fails if the application server has not been previously started.
Description: The deployment process tends to fail when a user tries to re-deploy an application without having previously started the application server.
Workaround: Start the application server, undeploy and deploy the application.
NetBeans 6.1 C/C++ support C and C++ applications on
Microsoft Windows, Macintosh OS X, Linux, and the
SolarisTM Operating System. C/C++ developers can
bring existing applications into the NetBeans project system, or develop new
applications and libraries. NetBeans C/C++ support covers the end-to-end
development cycle: projects and templates, an advanced language-aware editor,
makefile-based builds, and debugging.
The unresolved C/C++ issues for this release are as follows:
Issue
131946: Get a warning when trying to edit C files
Description: When you import settings from a NetBeans IDE 6.0-based
user directory to a NetBeans IDE 6.1-based user directory, you might
encounter problems such as not being able to edit source files. To avoid
such problems, do not import settings when you start using NetBeans
IDE 6.1 so that you start with a new user directory.
Issue
132946: Null pointer exception when opening project created with a
later version of NetBeans IDE.
Description: When you open a project created with a later
version of the NetBeans IDE, you might get a null pointer exception. If
this situation occurs, exit and restart the IDE, and then open the
project.
Issue
132203: Cancelling process does not kill running process
Description: When you try to cancel a running project by
right-clicking the progress bar in the lower right corner of the NetBeans
IDE and choosing Cancel process, the progress bar disappears but the
process continues running.
Issue #
121776: Sun Studio compiled code sometimes has problems being debugged with gdb
Description: On the Solaris and Linux operating systems, code
compiled with the Sun Studio compilers cannot always be correctly debugged
with the gdb debugger. Most known problems are fixed in the Sun Studio 12 software but
several more exist. If you run into problems
debugging programs compiled with Sun Studio 12 compilers, the first thing you
should do is apply the latest Sun Studio 12 product patches. If your problem
still exists, please file a defect in Issuezilla and make this task
depend on it.
As problems are found, we will open new issues and update this task to
depend on them, giving some idea of the current state of debugging programs
compiled with Sun Studio
12 compilers using NetBeans and the gdb debugger.
These problems do not affect debugging code compiled with Sun Studio 12
compilers using the Sun Studio 12 IDE and the dbx debugger.
Issue
#121775: Need latest Xcode for debugging on Tiger (Mac OS X 10.4)
Description: When debugging on the Macintosh with Tiger (Mac OS
X 10.4), the
default version of the gcc and g++ compilers generates
code with a bug in the debug output. Apple has released an updated Xcode package
(version 2.5) with a fix for this problem. The correct versions of gcc, g++,
and gdb are:
gcc: 4.0.1 - Apple build 5367
g++: 4.0.1 - Apple build 5367
gdb: 6.3.50 - Apple build 573 (10/20/2006)
This problem is not an issue on Leopard (Mac OS X 10.5).
The symptoms of the problem are that executables compiled with the
-gdwarf flag (the default for C/C++ application projects) have
incorrect line information and breakpoints may be ignored.
You can find news, articles, additional modules, and other useful information on the NetBeans project web site.
Since NetBeans is an open-source project, the web site also provides access to source code, a bug database, information on
creating your own NetBeans modules, and much more. For more information, visit
http://www.netbeans.org.
Documentation
To get the most out of the new functionality in NetBeans IDE 6.1, check out the
continuing series of web-based tutorials and flash videos. Keep checking these pages,
as we are adding new content all the time.
Note: Screencasts are for NetBeans IDE 6.0 and some may also function in NetBeans IDE 6.1.
The built-in help system for NetBeans IDE 6.1 has been updated to reflect the changes
in the user interface since release 5.5.
Note: If you are running the NetBeans IDE on Mac OS X, see Using
NetBeans on Mac OS X for more information about keyboard equivalents,
tips and tricks, and other Mac-specific topics.
Community
You can also keep up to date on NetBeans IDE and interact with the NetBeans community
by signing up for NetBeans project mailing lists at http://www.netbeans.org/community/lists/.
