Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The <Include-Resource> instruction is a list of arbitrary resources that should be copied into the bundle JAR file. The specified resources are declared as clauses that can have the following forms:

No Format
 
iclauseclause ::= assignment | inline | simple
assignment ::= PATH '=' PATH
simple ::= PATH
inline ::= '@' PATH

In the case of assignment or simple forms, the PATH parameter can point to a file or directory. The simple form will place the resource in the bundle JAR with only the file name, i.e., without any path component. For example, including src/a/b.c will result in a resource b.c in the root of the bundle JAR. If the PATH points to a directory, the directory name itself is not used in the bundle JAR. If a resource must be placed in a subdirectory of the bundle jar, then use the assignment form. The inline requires a ZIP or JAR file, which will be completely expanded in the bundle JAR.

<Import-Package>

The Import-Package header lists the <Import-Package> instruction is a list of packages that are required by the bundle's contained packages. The default for this header is "*", resulting in importing all referred packages. This header therefore rarely has to be specified. However, in certain cases when there is an unwanted import. The import is caused by code that the author knows can never be reached. This import , such an import can be removed by using a negating negation package pattern. For example:
Import-Package: !org.apache.commons.log4j

Anchor
default-behavior
default-behavior

...