Figure 9.16 One nice feature of Osmorc is that it allows you to choose whether to manage your man-
ifests yourself, or to have your manifests managed for you based on your module dependencies.
Unlike most of the tools we've discussed, Osmorc is designed to support both mani-
fest-first and code-first styles of development (see figure 9.16).
If you opt to have Osmorc manage your manifests for you, you have a choice
between using Osmorc's native support (which is based on bnd under the covers),
providing .bnd files, or using SpringSource's Bundlor. If you use the Osmorc support,
there's a GUI editor for specifying required properties like the bundle symbolic name.
You can also specify extra required entries in a text box. These entries are passed to
bnd before being written to the manifest file, so you're not restricted to normal mani-
fest syntax. This means you can use regular expressions and variable substitution. As
with plain bnd, it's important to specify your package exports, rather than allowing all
your bundle internals to be exported (see figure 9.17).
Figure 9.17 When you opt to let Osmorc manage your manifests, you can point it to a bnd file, or fill
in a simple panel on the module settings page with bnd-style settings. Don't forget to narrow down
the default package exports.
Search WWH ::