The denoted archive is used to lookup classes which are required by classes contained in this bundle.

The value of the meta-data is a VersionRange that specifies the build system version number range that the dependency should be applied to. If the current build system version constraint is not included in the specified version range, the associated dependency will be omitted.

This works similarly to MANIFEST_NAME_CLASSPATH_SUPPORTED_BUILD_SYSTEM_VERSIONS, but is declared on a dependency level instead of on the bundles.

Dependency resolvers may or may not take this meta-data into account. The repository will use this meta-data when creating the ClassLoader for the bundle.

The value of the meta-data is a VersionRange that specifies the JRE major version number range that the dependency should be applied to. If the current JRE version constraint is not included in the specified version range, the associated dependency will be omitted.

This works similarly to MANIFEST_NAME_CLASSPATH_SUPPORTED_JRE_VERSIONS, but is declared on a dependency level instead of on the bundles.

Dependency resolvers may or may not take this meta-data into account. The repository will use this meta-data when creating the ClassLoader for the bundle.

E.g. This meta-data name can be used to load different bundles on different Java versions:

 bundle.for.jdk8
     classpath: [0)
         jre-version: 8
 bundle.for.jdk9
     classpath: [0)
         jre-version: 9
 

The value of the meta-data is a comma separated architecture list that contains the architectures the dependency applies to. If the current architecture constraint is not included in the specified list, the associated dependency will be omitted.

This works similarly to MANIFEST_NAME_CLASSPATH_SUPPORTED_ARCHITECTURES, but is declared on a dependency level instead of on the bundles.

Dependency resolvers may or may not take this meta-data into account. The repository will use this meta-data when creating the ClassLoader for the bundle.

E.g. This meta-data can be used to load different bundles for different architectures:

 bundle.for.x86
     classpath: [0)
         native-architecture: x86
 bundle.for.x64
     classpath: [0)
         native-architecture: amd64
 

The denoted bundle dependency is not required for the safe operation of this bundle.

A private bundle dependency is considered to be an implementation detail for the bundle. The bundle doesn't publish data from a private through it's API.

The value of the meta-data is a VersionRange that specifies the Nest repository version number range that the dependency should be applied to. If the current repository version constraint is not included in the specified version range, the associated dependency will be omitted.

This works similarly to MANIFEST_NAME_CLASSPATH_SUPPORTED_REPOSITORY_VERSIONS, but is declared on a dependency level instead of on the bundles.

Dependency resolvers may or may not take this meta-data into account. The repository will use this meta-data when creating the ClassLoader for the bundle.

The file contains BundleDependencyInformation data in the format specified by BundleDependencyInformation.readFrom(InputStream, BundleIdentifier).

The this tokens in version ranges will be resolved to be the same as the enclosing bundle.

The "classpath" dependency kind is used to create the runtime ClassLoader for the classes in the bundle. These dependencies are transitively resolved to create the classpath for the bundle.

The classpath dependencies can have various meta-datas that can be used to configure the classpath loading for various environments. See the DEPENDENCY_META_* constants declared in this class.

The file contains ExternalDependencyInformation data in the format specified by ExternalDependencyInformation.readFrom(InputStream).

Dependencies declared with the "classpath" kind will be added tot he runtime classpath of the bundle.

The classpath dependencies can have various meta-datas that can be used to configure the classpath loading for various environments. See the DEPENDENCY_META_* constants declared in this class.

If a bundle entry is present at the value of this constant, then that file is used to read the declared tasks in the bundle. The file must have the following format in each line:

 [task.name]=[class-name]
 

Comments are not allowed.

The task name part must have the format defined by the TaskName class. It must not have qualifiers.

The class name must be the binary name of the task. It will be verified that the associated class file is present in the bundle.

Duplicate task declarations may not exists.

Allowed values are:

• 1: The initial version.

The manifest attribute is required and must contain a valid BundleIdentifier for the bundle.

This manifest attribute can be used to specify comma separated names that should be included in the classpath when loading the ClassLoader for this bundle.

Currently the following special classpath dependencies are allowed:

• SPECIAL_CLASSPATH_DEPENDENCY_JDK_TOOLS with the value jdktools.

The value is a comma (,) separated list of architecture names that the bundle classpath can be loaded on.

When the bundle classpath is loaded, the JVM reported architecture (os.arch property) is used to test if the bundle supports it. The architecture value is searched for in the attribute value. It is compared in a case-sensitive way.

If the manifest attribute is not specified, no restriction is placed for the supported architectures.

If the attribute is specified, it must specify at least one architecture, it cannot be empty.

The value of the attribute is a VersionRange that specifies the allowed build system versons on which the bundle's classpath can be loaded. The full version of saker.build is tested for the specified range.

If the attribute is not specified, no restriction is placed on the build system version.

The value of the attribute is a VersionRange that specifies which version can the enclosing bundle's classpath loaded on. The version range may only contain version numbers with a single major number. E.g.

• 8: The bundle may be loaded only on version 8. Same as [8].
• [8, 10]: Allows the bundle to be loaded on JDK 8, 9, and 10, but not on later versions.
• {8, 10, 12}: The bundle may be loaded only on versions 8, 10 and 12.
• 8.0.1: Invalid version range, as it may only contain version numbers with a single component.

The value of the attribute is a VersionRange that specifies the allowed repository versons on which the bundle's classpath can be loaded. The full version of the Nest repository is tested for the specified range.

If the attribute is not specified, no restriction is placed on the repository version.

The bundle that is specified by the value of this attribute is considered to contain the documentation for this bundle. The format of the files are unspecified. It may include documentation for different languages as well.

The bundle that is specified by the value of this attribute is considered to contain the sources for this bundle. The format of the files are unspecified. It may include sources from different languages, other from Java as well.

Requires the Java compiler related classes as the parent to the bundle class loader.
On JDK8 this works the same way as SPECIAL_CLASSPATH_DEPENDENCY_JDK_TOOLS, it loads the tools.jar for the classpath.
On later JDK versions, the repository runtime will load the jdk.compiler module in a way that it opens its packages to the bundle classloader. This means that the bundle classes will be able to access non-exported classes and packages from the jdk.compiler module.

Special care should be taken as the jdk.compiler module is essentially reloaded by the repository runtime. Its classes will be defined multiple times in the same JVM specifically for the repository operation. Bundles that use this feature should perform testing on the JDK versions it's expected to run. You will not be able to typecast object from the opened jdk.compiler module to types in the boot jdk.compilermodule.

If both this value and "jdktools" are specified, this takes precedence.

Requires the Java compiler related classes as the parent to the bundle class loader.
On JDK8 this will mean that the tools.jar in the JDK will be loaded and used as parent.
On later JDK version the platform class loader will be present as a parent class loader.