Optional.

File containing Netbeans-specific manifest entries. The plugin automatically generates some of the entries:

OpenIDE-Module-Implementation-Version: ${pom.currentVersion}
OpenIDE-Module: ${maven.nbm.modulename}
OpenIDE-Module-Specification-Version: normalized version of ${pom.currentVersion}
            
            

etc.etc.

If you define any of the entries in your manifest file, it overrides anything that gets automatically generated.

Optional. Default value is false.

Determines if the module is an autoload module or not.

A module cannot be both eager and autoload.

Optional. Default value is false.

In version 0.1 the default was true, incompatible change.

If true, the application restarts after installation of the module. Required generally only when the nbm includes files in netbeans/lib subfolder. (AFAIK)

Since 0.3

Optional. Default value is License for ${pom.name}.

Name of the license file to be included with the nbm. Eg. Apache License, Version 2.0

Since 0.6

Optional. Default value is ${maven.build.dir}/nbm.

The output directory of the nbm plugin. The modified project's artifact is placed here. Later also the nbm file for the project.

The plugin will create a netbeans/${maven.nbm.cluster.name} subdirectory in here where all the files are placed that are later put into the nbm. Regular Netbeans directory/file layout applies.

You might want to make use of this property when you want to merge multiple projects belonging to one cluster and create an installation for it.

OPTIONAL. Allowed types are loose, spec, impl

If the property is set on the dependency, it is expected to be a Netbeans module dependency. When the project is built using the nbm:jar goal, it will build a OpenIDE-Module-Module-Dependencies manifest attribute. Again it will only be included in the jar, unless you define your own custom manifest attribute in the manifest file. These dependencies are expected to be present in the IDE when deploying. All of them should be Netbeans modules, not necessarily at build time, but definitely at runtime (installation).

For example:

       <dependency>
           <groupId>forehead</groupId>
           <artifactId>forehead</artifactId>
           <version>1.0-beta-5</version>
           <properties>
            	<netbeans.module.dep>impl</netbeans.module.dep>
            </properties>
        </dependency>
        
        <dependency>     
           <groupId>netbeans</groupId>
           <artifactId>org-netbeans-modules-projectuiapi</artifactId>
           <version>1.0-SNAPSHOT</version>
           <type>jar</type>
           <properties>
                <netbeans.module.dep>spec=org.netbeans.modules.projectuiapi/0 &gt; 1.0</netbeans.module.dep>
           </properties>
        </dependency>
        
                        

There are 3 types of allowed values:

loose creates a dependency in the format org.openide.execution It's very loosely coupled and it just expects some version of the dependency module to be present and enabled.

spec creates a dependency based on the specification number. In the module's manifest it looks like this: org.openide.execution > 1.0.1 The module will work with any subsequent version of the dependency module (unless that one breaks backward compatibility). The version number to can be explicitly specified as is shown in the example above or the plugin will try to guess it. The dependency jar is examined and if it is a netbeans module, its specification number and module name are used. The dependency version from the pom is used as fallback.

impl creates a dependency based on the implementation number. It looks like this: org.openide.execution = 1.0.1 It will require a specific version of the dependency module. Use only when you depend on a non-public feature or code that was changed in later versions or could be changed. The version number to can be explicitly specified or the plugin will try to guess it. The dependency jar is examined and if it is a netbeans module, its implementation version and module name are used. The dependency version from the pom is used as fallback.

Optional. Since 0.2. Default value is ?.

Shall contain path the keystore file.

Optional. Since 0.2. Default value is ?.

Alias in the keystore for signing the nbm.

Since 0.2

Optional, required for nbm:autoupdate goal. Default value is "NBM_AutoUpdate"

Name for the xml file describing the autoupdate server content information.