...
- Use the parent for extension modules.
- The
artifactId
will be used with the group idgroupId
to generate the manifest headerOpenIDE
-Module-Module
. ThegroupId
andversion
are inherited from parent herein this case.version
will generate the manifest headersOpenIDE-Module-Specification-Version
andOpenIDE-Module-Implementation-Version
, the latter will include a timestamp. - Packing must always be nbm to generate NBM files.
- Name will generate the manifest header
OpenIDE-Module-Name
. - Description will be used to generate
OpenIDE-Module-Short-Description
- This 3rd-party dependency will result in a private JAR located in ${cluster}/modules/ext/org.esa.snap.mymod/jdom2.jar. Another NB module depending on mymod and wanting to use jdom2 does not need to import it explicitely again as long as you export its API as a public package(s). See below. If you don't export the jdom2 API, a second private ext-JAR will be created in the cluster.
- The following are NB-module dependencies from which the manifest header
OpenIDE-Module-Module-Dependencies
will be derived. - Required declaration of the Maven NBM plugin.
- Optinally export the 3rd party jdom2 API so that other modules don't need to import the JAR.
- Optionally export API from myext.
Note thatorg.esa.snap.myext
only exports classes in themyext
package, while the valueorg.esa.snap.myext.*
exportsmyext
plus all subpackages, recursively. - Required declaration of the Maven JAR Plugin.
useDefaultManifestFile
must be set totrue
.
...