| <html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 5. Manifest Templates</title><meta content="DocBook XSL Stylesheets V1.76.0" name="generator"><link rel="home" href="index.html" title="Bundlor User Guide"><link rel="up" href="index.html" title="Bundlor User Guide"><link rel="prev" href="ch04s03.html" title="Apache Maven Usage"><link rel="next" href="ch05s02.html" title="Manifest Template Format"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><td align="left" width="20%"><a accesskey="p" href="ch04s03.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch05s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 5. Manifest Templates"><div class="titlepage"><div><div><h2 class="title"><a name="manifest.template"></a>Chapter 5. Manifest Templates</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch05.html#manifest.template.introduction">Introduction</a></span></dt><dt><span class="section"><a href="ch05s02.html">Manifest Template Format</a></span></dt><dt><span class="section"><a href="ch05s03.html">Specifying property placeholders</a></span></dt><dt><span class="section"><a href="ch05s04.html">Specifying automatic version expansion of imported packages based on a pattern</a></span></dt><dd><dl><dt><span class="section"><a href="ch05s04.html#manifest.template.format.version.naming">Re-using version patterns</a></span></dt></dl></dd><dt><span class="section"><a href="ch05s05.html">Example Bundlor Manifest Template</a></span></dt></dl></div><div class="section" title="Introduction"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="manifest.template.introduction"></a>Introduction</h2></div></div></div><p> | |
| A manifest template is a file that Bundlor uses during the generation of OSGi-compliant manifest entries in | |
| a JAR's manifest. The format of the manifest template is the same as that of a standard Java manifest file, | |
| i.e. a series of '<code class="literal">key: value</code>' pairs. | |
| </p><p> | |
| From this template, Bundlor recognizes a specific set of directives and uses them to generate the | |
| OSGi-compliant manifest entries. Bundlor will also add any other headers that are specified in the template | |
| to the generated manifest. This is typically used to specify things like the bundle's symbolic name and | |
| version. | |
| </p><p> | |
| You can also specify property placeholders, or variables, in your manifest template that Bundlor substitutes | |
| with actual values at runtime. With this feature, your manifest templates become more dynamic and useful | |
| across a variety of your projects. A particularly handy use for this feature is to tell Bundlor to | |
| automatically expand versions of imports based on a pattern of your choosing. See | |
| <a class="xref" href="ch05s03.html" title="Specifying property placeholders">Specifying property placeholders</a> for details. | |
| </p></div></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch04s03.html">Prev</a> </td><td align="center" width="20%"> </td><td align="right" width="40%"> <a accesskey="n" href="ch05s02.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%"> </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> </td></tr></table></div></body></html> |