From Wikipedia article:
- "The NetBeans IDE is written in Java and can run anywhere a compatible JVM is installed, including Windows, Mac OS, Linux, and Solaris. A JDK is required for Java development functionality, but is not required for development in other programming languages."
As you can see on the download page , Netbeans is actually segmented into different flavors, each made for a specific use case. There is also a version gathering all the different flavors together.
If you want to install all the flavors at once, install the package or AUR.
If you want a specific flavor, in order to have a minimal installation for example, install one of the following packages:
- Java SE: AUR or AUR;
- Java EE: AUR or AUR;
- C/C++: AUR or AUR.
Please note the
-nightly versions are actually binaries versions compiled everyday from the trunk branch from the development repository.
Tips and tricks
/usr/etc/netbeans.confwill be overwritten during updates. To keep changes add them to your local netbeans.conf
~/.netbeans/version/etc/netbeans.conf(you will need to create the etc dir and the .conf file).
- Settings in local version of netbeans.conf override the same settings in the global copy of the file.
- Command-line options override settings in either of the configuration files.
Font antialiasing in Netbeans
As Netbeans is written in Java, the font rendering is managed by Java itself and also by Netbeans. Modifying the font antialiasing parameters can thus happen at two levels:
- In the Netbeans configuration. If the file is missing, you may need to create it.
[...] netbeans_default_options="[...]-J-Dswing.aatext=TRUE -J-Dawt.useSystemAAFontSettings=on" [...]
Look and feel
To change Netbeans look and feel, go to Tools > Options > Appearance > Look and Feel
To add a dark look and feel to the GUI but also to the colorschemes used in the code, you can install one of the following certified extensions from the plugin directory which can be reached from Tools > Plugins > Available Plugins:
- Dark Look And Feel Themes
- Darcula LAF for NetBeans: which, as of January 2017, better integrates with current desktop environments and mimic the default Darcula look and feel from used in IntelliJ IDEA or Android Studio.
Integrate with the Apache Tomcat Servlet Container
It is possible to debug web applications running on Tomcat from within Netbeans, using stock Arch packages for both Netbeans and Tomcat. While this section is written for
tomcat7, this applies to all versions of Tomcat currently in the repositories.
- First install your desired version of Tomcat, such as Tomcat). (see also
- While you can modify the configuration files in
/etc/tomcat7to work with Netbeans debugging, it is recommended you create local copies and use those instead. That way, you still can run Tomcat as an ongoing system service, while debuggging with a different instance:
- Pick a location for the local configuration files, such as
~/.tomcat7and create that directory.
cp -r /etc/tomcat7 ~/.tomcat7/confand
chown -R $(id -un):$(id -gn) ~/.tomcat7, both with root privileges
- Pick a location for the local configuration files, such as
- Clean up the Tomcat users and permission file, so Netbeans can insert what it needs. Edit the tomcat user file without any user and role information in it:
<?xml version='1.0' encoding='utf-8'?> <tomcat-users xmlns="http://tomcat.apache.org/xml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://tomcat.apache.org/xml tomcat-users.xsd" version="1.0"> </tomcat-users>
- Make the "manager" app accessible from your local configuration:
ln -s /var/lib/tomcat7/webapps/manager ~/.tomcat7/webapps/manager
- Provide a temp directory:
- If needed, change the port at which Tomcat runs by editing
- Have Tomcat write its logs somewhere else than
- Unfortunately, Netbeans refuses to continue unless it can read
/etc/tomcat7/server.xml, so temporarily give the file
644permissions. Change the permissions back later.
Then, in Netbeans:
- Go to Tools > Servers > Add Server and select Apache Tomcat. Click Next.
- In Server location, specify
- Check Use Private Configuration Folder (Catalina Base) and specify the full path to directory
~/.tomcat7. This must be the full path, as Netbeans does not recognize the meaning of
- Finally, pick a username and password. Check Create user if it does not exist. This will configure Netbeans, but also add the user information to the
Note that this local instance of Tomcat will write its logs to
Integrate Netbeans with kwallet
Netbeans may need to store some passwords. It can do that in kwallet. See this article in the Netbeans wiki.
However, you need to install and configureAUR so that netbeans find the qdbus command:
$ ln -s /etc/xdg/qtchooser/4.conf ~/.config/qtchooser/default.conf
See forum discussion 
Maven problems with small tmpfs
If your system has a small tmpfs partition you will have problems unpacking the maven index (will continue downloading again after failing to unpack). To fix this issue, append the following pieces of information in the Netbeans configuration file accordingly.
[...] netbeans_default_options="[...]-J-client -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true -J-Dsun.java2d.dpiaware=true -J-Dsun.zip.disableMemoryMapping=true -J-Djava.io.tmpdir=/path/to/tmp/dir" [...]
Wrong Directory for JDK/JRE
It might be that after installation, netbeans_jdkhome is set incorrectly:
[...] netbeans_jdkhome="/tmp/yaourt-tmp-x230a/aur-netbeans-cpp/pkg/netbeans-cpp/usr/share/netbeans/bin/jre" (example) [...]
Just comment out this line, netbeans will find the proper path on startup. Since netbeans.conf might be overwritten during an update, this procedure might need to be done again after an update, or you put netbeans_jdkhome into the config in your home directory (see above).
Plugin installation fails due to lack of unpack200
The unpack200 was removed in jdk version 14, causing plugin installation in Netbeans to fail. As a workaround, one can set
/usr/share/netbeans/etc/netbeans.conf to earlier jdk version. After plugin installation you can return to default jdk, but this will have to be repeated for each plugin update.