Page History

...

clause ::= assignment | inline | simple
assignment ::= PATH '=' PATH
simple ::= PATH
inline ::= '@' PATH

For the <Include-Resource> instruction, actual file paths are relative to the pom.xml, while file copies are relative to the root of the resulting bundle JAR file. 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 entire directory name itself is not used in the bundle JARhierarchy is copied into the resulting bundle JAR file relative to the specified directory. If a resource must be placed in a subdirectory of the bundle jar, then use the assignment form. The inline form requires a ZIP or JAR file, which will be completely expanded in the bundle JAR.

...

• <Bundle-SymbolicName> is assumed to be "${groupId}.${artifactId}".
• <Export-Package> is assumed to be "${groupId}.${artifactId}.*", which copies everything under the project package root into the bundle and exports it.
• <Import-Package> is assumed to be "*", which imports everything else not in the bundle.
• <Include-Resource> is assumed to be empty, since Maven automatically copies "src/main/resources/", which will copy the directory hierarchy into the resulting bundle JAR file, mirroring standard Maven behavior.
• <Bundle-Version> is assumed to be "${pom.version}" with '-' characters replaced with '.' characters.
• <Bundle-Name> is assumed to be "${pom.name}".
• <Bundle-Description> is assumed to be "${pom.description}".
• <Bundle-License> is assumed to be "${pom.licenses}".
• <Bundle-Vendor> is assumed to be "${pom.organization}".

...