If a longer message is logged the ant logger will handle the message as plain text and will not try to hyperlink, color, fold, etc. If not set by the user a default value of 3000 will be used.

This system property is causing the breakpoints view to show also hidden breakpoints.

Logging level for informational messages about breakpoint submission and hits. They use Level.FINE and Level.FINER levels and are printed into the NetBeans message log.

When this system property is set, informational messages about start of JPDA debugger are printed into standard output (console).

This system property sets the debug mode of the debuggee virtual machine via VirtualMachine.setDebugTraceMode() method. See the javadoc of that method for the description and possible values.

Logging level for informational messages about received JDI events. They use Level.FINE level and are printed into the NetBeans message log.

When this system property is set, informational messages about the smart stepping process are printed into standard output (console).

When this system property is set, methods invocation in debuggee is disabled.

Logging level for messages about method invocation. They use Level.FINE level and are printed into the NetBeans message log.

Logging level for messages about variables evaluation. They use Level.FINE level and are printed into the NetBeans message log.

When this system property is set, informational messages about the tasks that refresh debugger views are printed into standard output (console). The value of that property should contain 'w' for watches view, 'l' for local variables view, 'c' for call stack view, 's' for classes view and 't' for threads view.

Minimum integer level that triggers the blinking icon signaling an exceptional state. By default 900 - e.g. WARNING.

Minimum integer level that triggers the dialog with exception. By default 900 with assertions on and 1001 without them.

Main Java class for bootstrap code to start (currently org.netbeans.core.startup.Main). Might be used by alternate launchers.

NetBeans installation directory (where the launcher is).

If this property is provided, it is used as the current working directory regardless of the value of user.dir.

Additional secondary NetBeans installation directories as proposed in installation structure design document.

Alternative location of NetBeans fallback cache generated during installation (see installation cache for description of the files layout). If the property is set to none, then the fallback cache check is completely disabled.

Classpath to prepend to core loader (normally just lib/*.jar). Possibly useful for testing infrastructure etc.

By setting this system property to a classpath (list of directories and JARs separated by the normal path separator) you may append to the system class loader.

By setting a system property to "netbeans.patches." + module.getCodeNameBase() one can influence installed modules without changing the build. Format is -Dnetbeans.patches.org.nb.mods.foo=/path/to.file.jar:/path/to/dir.

There is a special support for importing the settings from previous versions. As only the product itself knows about what to import and where this cannot be done directly in the launcher, but we need at a well defined moment (user directory is missing and no modules have been initialized yet) to call the product to ask the user and do the actual copy of userdir.

After all core/*.jar files has been initialized and the user dir has not yet been updated (see bellow) the launcher checks for value of netbeans.importclass system property and if provided it loads that class and invokes its main method (in AWT thread) and if no exception is thrown it marks the userdir as already upgraded.

Before first usage of IDE user must accept license. If user does not install IDE by installer (user must accept license during installation) user must accept license during IDE first start.

Launcher calls method showLicensePanel of netbeans.acceptlicenseclass if license was not yet accepted by user and it is necessary to show license in dialog to user.

Controls whether to log messages to the console, or just to the log file.

Setting this property to less than zero value enables logging of what is going on in the CLIHandler - e.g. in the code that locks user directory and handles processing of command line options. Use -J-Dorg.netbeans.CLIHandler=-1 to send the logging to System.err.

One can disable the CLI server (listening on commands from subsequent invocations) by setting property org.netbeans.CLIHandler.server to false.

Contains class name of a class that can serve as provider of the writable layer of the system file system. The class must be a subclass of org.openide.filesystems.FileSystem and have public default constructor. Morevoer the class denoted by the property must be on the classpath.

By default NetBeans prevent certain operations like System.exit. One can disable this behavior by providing -Dnetbeans.security.nocheck=true. Since version 2.47 such property also allows the SecurityManager to be replaced by another.

Specifies the amount of milliseconds the call to getContent() method of ExClipboard waits to synchronize with system clipboard. Defaults to 1000ms.

By default ModuleManager throws DuplicateException when an attempt is made to load an already loaded module. One can change this behavior by providing -Dnetbeans.ignore.dupmodule=true since version 2.63. When -Dnetbeans.ignore.dupmodule=true is provided, attempt of duplicate loading is logged instead of throwing DuplicateException.

For backward compatibility, the NetBeans startup code performs bytecode manipulation such as making marked methods public or injecting code that was deprecated and removed from the NetBeans codebase. For debugging, or simply in order to disable preprocessing, patching may be disabled. Note that older modules, which were not recompiled against the released version's sources may become broken, if bytecode patching is disabled.

Set this property to true to workaround the bug #50423 which appears on some linuxes on JDK 1.5.

Set this property to true if you do want to cleanup the module system, but not call System.exit at the end. Used from NbModuleSuite from nbjunit library.

This module contains a hook to identify long running tasks inside the AWT dispatch thread. It observers the AWT event queue and if a task takes longer than expected, it invokes a sampler that creates a profiling snapshot of the IDE until the task returns back to the event queue. Time limits can be configured via system properties (in milliseconds):

• org.netbeans.core.TimeableEventQueue.quantum=xyz - for how long the event queue must be blocked to start the self-sampler (by default 100ms),
• org.netbeans.core.TimeableEventQueue.report=xyz - total time of blocked event queue to report a problem (by default 3s),
• org.netbeans.core.TimeableEventQueue.waitcursor=xyz - time for which a problem is not reported if mouse wait cursor is in place (by default 15s),
• org.netbeans.core.TimeableEventQueue.pause=xyz - time after reporting a problem for which the detection is disabled (by default 15s).

In production builds the default time limits are different (10s to start sampler, 20s to report a problem).

System.getProperties() that start with prefix felix. or org.osgi.framework. are read on initialization of the Netigso system and injected into configuration of OSGi container before it starts.

If started with -J-Dorg.netbeans.log.startup=print parameter, then times of various start operations are printed to console. If the value is -J-Dorg.netbeans.log.startup=file then the values are printed into file specified by -J-Dorg.netbeans.log.startup.logfile=filename. Since NetBeans 7.1 one can also fill in the file by standard XML format of log messages by using -J-Dorg.netbeans.log.startup=xml.

Moreover if any module logs data to Logger.getLogger("org.netbeans.log.startup") with calls like log(Level.FINE, "start", "msg") and log(Level.FINE, "end", "msg") or log(Level.FINE, "progress", "msg"), then these messages are collected into the start log as well.

Allows unit tests to prevent changes to System.err and System.out by the logging infrastructure.

Changes the number of files used for log rotation. If started with -J-Dorg.netbeans.log.numberOfFiles=number then the log files for number-1 previous executions will be preserved. Default and minimum number is 3.

Disables #113341 so that the first version of a module JAR to be encountered is loaded, even if a later cluster contains a newer version of the same module.

This property can contain name of a class implementing FileSystem with a public default constructor. Such filesystem is then used during initialization of writable layer of system file system (see getConfigRoot). The filesystem may use or may ignore value of System.getProperty("netbeans.user").

Note: The class is loaded sooner then modules are initialized, as such the class providing it must be from a JAR file placed in to $cluster/core/ directory. Such JAR may have just a limited dependencies - e.g. only module system and filesystem API.

Similar to OSGi's org.osgi.framework.bootdelegation property. Allows unit tests (or even regular code) to prevent classloading from application classloader for other, then explicitly enumerated packages.

This property shall contain a set of comma separated values of package names. Classes from those packages will be loaded by the classloader framework from application classloader. If the name of a package ends with .* suffix, all packages under the given package name are allowed for delegation (but not the package by itself).

The classes from the java.* namespace are allowed and do not need to be enumerated at all. If this property is not specified at all, all classes visible by the application classloader can be accessed. Available since version 1.26.

This property includes the display name presented to the user as Product Version in the About dialog box and in the log file.

Some applications built on top of NetBeans Platform expressed an option that certain files in caches, namely all-resources.dat can be too big and that this is not good for multi-user installation. To give such applications control over creation of this file, there is a property to (conditionally) disable the creation of the cache file.

Change value of org.netbeans.core.update.all.resources property in launcher configuration file or provide it as a virtual machine parameter on command line. Set it to never, always or missing. The default is to regenerate and update the cache always. Value missing means to generate the cache only if it has not been previously available (even in installation location). Setting the value to never will disable the creation of the cache after start completely.

Changing default value of the property may be particulary useful when there is a shared installation of the application, there are many users with a home (and cache) directory on a slow (network) file system and it is expected most of them won't install additional modules into their own user directory.

Setting this property affects the associated module autoupdate.ui. Setting it to true results in the detailed view (all visible plugins) been selected when Installed tab is opened in Plugin Manager. Otherwise the simple view (high-level features) is selected.

You can suppress automatic reporting of slow code completion computation by increasing value of -J-Dorg.netbeans.modules.editor.completion.slowness.report property to more than 2000 ms (the default value).

This property sets the logging level. See org.openide.ErrorManager.getInstance for more details.

Starting NetBeans with netbeans.debug.gradle.info.action=true would make the Gradle project information loading into a debugabble JVM where the debugging port is 5006. A new debugger session can be attached to that port, make the netbeans-gradle-tooling project debuggable in action.

If the property is set to true the project updates metadata of project.xml from the namespace http://www.netbeans.org/ns/j2se-project/1 to http://www.netbeans.org/ns/j2se-project/2 without explicit user confirmation.

If set to true, displays a truncated version of Java package names, usually in the Projects tab.

If a longer message is logged the ant logger will handle the message as plain text and will not try to hyperlink, color, fold, etc. If not set by the user a default value of 3000 will be used.

If set to true, displays a truncated version of Java package names, usually in the Projects tab.

If a longer message is logged the ant logger will handle the message as plain text and will not try to hyperlink, color, fold, etc. If not set by the user a default value of 3000 will be used.

When the ensure.built.source.roots property is set during ant script execution, the javac task will not actually build the classfiles from scratch, but rather copy classfiles produced by the Java infrastructure into the output folder. The content of the property will be interpreted as list of source roots, for which the artifacts should be copied.

If set to true, *.class files generated by external build processes will not be overwritten by the IDE’s Java parser when running in “compile-on-save” mode unless the class files are older than the corresponding source file.

It is possible to disable native listening on filesystem changes. Useful mostly in testing environment, but it may be interesting for some users too. Don't rely (much) on this property from production code however.

It is possible to enable use of FAM notifier on Solaris disabled by default. Useful mostly in testing environment, but it may be interesting for some users too. Don't rely (much) on this property from production code however.

To address problems when mixing various types of network file systems (as described in bug 198946) there is a special property org.netbeans.modules.masterfs.case that can be set to sensitive or insensitive value in order to override the system default. This is intended only for end user consumption, not for consumption by other parts of the system. The name and meaning of this property may change in any release.

Native listeners check the org.netbeans.io.suspend property. If it is set to integer greater than zero, they stop delivering file change events. The list of modified directories is recorded (its size is made available by setting its string value into org.netbeans.io.pending property), but its processing is suspended. Events are delivered when org.netbeans.io.suspend property changes its value to 0 or becomes empty.

I/O intensive operations in other NetBeans modules are advised to honour the org.netbeans.io.suspend property as well and suspend their I/O activities too.

In order to properly communicate changes to the property between multiple receivers and multiple controllers it is suggested to only manipulate the value under synchronized("org.netbeans.io.suspend".intern()) lock. Those changing the value are supposed to increment it by one when they request the suspend and decrement it by one when they want to resume their own suspend.

Whenever a change to the state of the property is made, controllers are supposed to "org.netbeans.io.suspend".intern().notifyAll().

A system property can be used to change the default indexing sleep delay during builds, in case reparsing starts too soon (wasting CPU) or too late (impeding editing).

used only when nbjunit.diff.impl is set to org.netbeans.junit.diff.NativeDiff class. This property contain command line, which is called from NativeDiff class to perform comparision. This property use also '%TESTFILE%' and '%PASSFILE%' variables understood by NbJUnit, which are replaced with real file names when running tests.

path to a directory, which is used as a root for tests' working directories (for details see JavaDoc for NbTestCase.getWorkDir()).

This property tries to influence the order of NbTestCase methods so it is more predicatable (see Order of elements for description of the problem). The acceptable values of the property are:

• "natural" - use the methods as provided by JDK (e.g. quite random on JDK7)
• "a-z" - sort the tests in ascending alphabetical order
• "z-a" - sort the tests in descending alphabetical order
• "shuffle" - randomize the order of the tests. If a test fails in this mode a seed is attached to the failure message, use it in the seed mode
• seed mode "12234390434" - one can specify any long value as a seed to shuffle the methods. Use this to reproduce random failures

The default order is natural right now, but this may change in future to mitigate the randomness caused by JDK7.

NbModuleSuite can now be influenced by system property branding.token. If it is provided (by Ant harness for example), it is used to call NbBundle.setBranding.

The "netbeans.do.not.check.xalan" property switches off the startup check for buggy Xalan. See issue #70130 for more information.

The "netbeans.do.not.check.xalan" property switches off the startup check for buggy Xalan. See issue #70130 for more information.

If defined, limits search for a parent project to a certain subtree. The property defines the absolute path of a folder where upwards search for a project in parent folders is terminated. Queries outside the root will not find any project. Multiple folders may be specified when delimited with OS-specific path separators (':' on *nix, ';' on Windows). Currently used for tests so the tested runtime does not escape the workdir.

When this property is set, the opening of projects doesn't trigger opening and focusing of the projects logical view top component. Allows the BlueJ Edition to focus it's own component instead.

Error manager logging category for things affecting project list.

Property for overriding default location of projects directory which is folder NetBeansProjects under $HOME on Unixes and under default user folder on Windows (e.g. C:\Documents and Settings\[username]\My Documents\NetBeansProjects). Directory passed by the property must exist, otherwise default is used.

For testing purposes one can specify different URL for upload of files, by setting org.netbeans.modules.uihandler.Submit property when invoking NetBeans.

For testing purposes one can specify different URL for upload of files, by setting org.netbeans.modules.uihandler.Submit property when invoking NetBeans.

System property "nb.show.statistics.ui" controls if UI for Usage statistics is displayed in General panel. If this property is non null (for IDE) UI is shown. This property contains key of preference used to save status - true if usage statistics are collected and uploaded, false if not. Key is "usageStatisticsEnabled" and is described below.

The system property nb.tabs.suppressCloseButton can be used to hide close buttons by default.

The system property winsys.stretching_view_tabs can be used to switch to stretching tab layout as implemented in NetBeans version 7.0 and older.

If set to true, changes default value of the asynchronous() method. Useful for unit tests which would prefer to run all tested actions synchronously.

Status text set in StatusDisplayer is by default shown in status line of NetBeans and is hidden after specified timeout. If not overriden by this property it is done after 5000ms. O means that the last text will be shown and not removed.

If System.getProperty("org.openide.awt.ActionReference.completion") is specified, then the dedicated processor for ActionReference tries to load such class, casts it to Processor and asks it for additional completion items for its path attribute. By default, when running inside NetBeans IDE, apisupport.project registers such class and provides items representing valid paths in current project.

Setting this property to integer number controls prefetching of nodes when VisualizerChildren are constructed (prefetchCount = 0 disables prefetching). The prefetching should eliminate "bounce" effect (see #144718) in lazy implementation which is caused by the fact that there exist keys without nodes. In such case "dummy" nodes are created and remove event is fired. This undesirable effect is eliminated by prefetching selected number of nodes so "dummy" nodes are detected and removed in advance before any visualization occurs.

Checks by Drag & Drop support for views. True is regard as default (no matter what jdk's version). False value disallows Drag & Drop in all views.

Name of attribute file can be changed , if .nbattrs can't be used.

Periodic refresh can be set.

If true, better diagnostic information will be available as to when file input or output streams were opened that prevent a file from being deleted because they were not closed. This information comes at a performance cost, however.

Used by FileChooserBuilder. If set to false, file choosers created by instances of FileChooserBuilder will traverse symlinks. By default they do not.

Used by FileChooserBuilder. If true, FileChooserBuilder will not remember users' recent directories across sessions. This property is provided for applications where a history of recently used directories is a security concern.

Since 7.25 the DataFolder.getNodeDelegate() tries to prevent creation of DataObject in AWT dispatch thread. Rather it creates dummy node with name derived from the name of the file and simplified content of lookup:

• FileObject - the file that the node represents
• Node - the node itself, but without any important properties
• DataObject - created on the fly, very inefficient, if requested from AWT dispatch thread, it prints a warning. Consider using just FileObject.

The creation of real node is scheduled to background and as soon as the DataObject and its Node are ready, the initial dummy node is replaced by the real one.

This whole system is slightly incompatible and may complicate creation of filtered views over the node hierarchy (one needs to be ready to really dynamics changes). That is why it is possible to disable the new delayed system by starting the system with -Dorg.openide.loaders.FolderChildren.delayedCreation=false. Use this property as a temporary fix for your problems, but consider fixing your code to support the delayed mode in the future.

The value of type integer determines the number of milliseconds between successive refreshes of contents of a folder. Can be used to tweak performance of folder refresh. Defaults to 10.

If set to true, the DataObject.copy, move, createFromTemplate are executed in insecure way. That means that other threads can access the products of such operation before it finishes. This is a friend contract with projects, that need to do such strange things. Will be removed when they fix it.

Classpath appended to the system class loader. Used for automated testing infrastructure.

By default true, may be turned off to disable manifest caching.

Patch directories or JARs to add to the class loader for a module, besides patches/MODULE-CODE-NAME-BASE/*.jar.

If true, all module classes are forcibly loaded at startup, to help detect possible linkage errors.

Disables automatic module dependency upgrades.

If set to 0, enables logging for the module system.

Disabled automatic transitive class loader dependencies for old modules.

Avoids text messaging (other than ErrorManager logging) to the console from the module system.

Suppresses checks to ensure that module section classes are actually loaded from the module itself.

Suppress security checks in the VM, even from "untrusted" code.

Prints messages when resources or classes are loaded from JARs.

Used to control the XML layer cache mechanism. Value may be a fully-qualified class name to load as a manager (implement org.netbeans.core.projects.cache.LayerCacheManager), or - to disable caching and always parse the XML layers directly. Current default is to use a binary cache manager.

Specifies the time in ms unused RequestProcessor processor threads remain around, until they get GCed. By default 60s. Primarily used from tests.

checked by the initialization of the Lookup.getDefault() and can contain name of a class that extends org.openide.util.Lookup and has public constructor, that should be instantiated and returned from Lookup.getDefault() the class will be loaded by Thread.currentThread().getContextClassLoader() classloader the first time Lookup.getDefault is invoked.

The property can also contain value "-" which means to completely disable the lookup instantiation and return Lookup.EMPTY from Lookup.getDefault().

If the property is unspecified, the default MetaInfServicesLookup is constructed for Thread.currentThread().getContextclassLoader() that implements the JDK's standard. If, by a chance an instance of Lookup.Provider is found in there, its lookup is returned as result. Otherwise the MetaInfServicesLookup is the result of Lookup.getDefault().

Sometimes it may be useful for the Lookup to contains objects from some system file system folder. This can be done with org.openide.util.Lookup.paths=Folder1:Folder2:Folder3. If this property is set prior to first call to Lookup.getDefault(), it is split into pieces (separator is ':') and individual parts are then used to construct Lookups.forPath("Folder1"), etc. All these lookups then become part of the Lookup.getDefault() one. This property works since version 7.24

Valid values are path to image in NB like "org/netbeans/core/resources/splash.gir". It puts the specified image into the the emptied documents area. it is experimental now. -J-Dnetbeans.winsys.imageSource=org/netbeans/core/resources/splash.gif

Valid values are "true" and "false". Default is "false". If it is "true" it paint faded feedback during DnD of windows. Keep in mind it makes some performance impact on DnD. It is experimental now. -J-Dnetbeans.winsys.fade.on=true

Valid values are "true" and "false". Default is "false". If it is "true" it disables DnD of windows. -J-Dnetbeans.winsys.disable_dnd=true

Valid values are "true" and "false". Default is "false". It allows user to move (e.g. using DnD) TopComponentS between editor(document) and view which is restricte otherwise. It is experimental now. -J-Dnetbeans.winsys.allow.dock.anywhere=true

Valid values are "true" and "false". Default is "false". If it is "true" it doesn't show empty documents area. -J-Dnetbeans.winsys.hideEmptyDocArea=true

Valid values are "true" and "false". Default is "false". If it is "true" it shows status line at the and of menu bar instead of the bottom of documents are (or main window). -J-Dnetbeans.winsys.statusLine.in.menuBar=true

Valid values are "true" and "false". Default is "false". If it is "true" it hides all toolbars. -J-Dnetbeans.winsys.no_toolbars=true

If this property is set its value must point to a file on the system file system that provides instance of type org.openide.awt.MenuBar. This alternative menu bar will be used instead of the default one. -J-Dnetbeans.winsys.menu_bar.path=foo/bar.instance

If this property is set its value must point to a file on the system file system that provides instance of type javax.swing.JComponent. This alternative status line will be used instead of the default one. -J-Dnetbeans.winsys.status_line.path=foo/bar.instance

Valid values are "true" and "false". Default is "false". If set to "true" the modal dialogs will be shown without the help button. -J-Dnetbeans.winsys.no_help_in_dialogs=true

If set to false, windows opened (e.g. TopComponent.open) using the dummy fallback window manager will not really be set to be visible. Useful for unit tests which must incidentally use the Window System API but for which actual display of windows is undesirable.