# Printing MANIFESTs of all .jar files in a folder

**URL:** <https://bnd.discourse.group/t/printing-manifests-of-all-jar-files-in-a-folder/543>\
**Category:** TIPS\
**Created:** [December 13, 2025, 11:20pm UTC](https://bnd.discourse.group/t/printing-manifests-of-all-jar-files-in-a-folder/543 "2025-12-13T23:20:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisrueger](https://yyz2.discourse-cdn.com/free1/user_avatar/bnd.discourse.group/chrisrueger/32/18_2.png) [@chrisrueger](https://bnd.discourse.group/u/chrisrueger)\
**Post date:** [December 13, 2025, 11:20pm UTC](https://bnd.discourse.group/t/printing-manifests-of-all-jar-files-in-a-folder/543/1 "2025-12-13T23:20:42Z")

</div>

## Use case

I recenlty OSGified an open source library using [bnd-maven-plugin](https://github.com/bndtools/bnd/blob/master/maven-plugins/bnd-maven-plugin/README.md#bnd-process-goal) to add OSGi meta data. It was a multi-module maven project resulting in one .jar file per module. I wanted to quickly view all MANIFEST.MF files of all jars in a text file.

Turns out the [bnd print](https://bnd.bndtools.org/commands/print.html) command of the [bnd CLI](https://bnd.bndtools.org/chapters/400-commands.html) can help.

## Examples

E.g. for a maven folder layout, run this in the root of your project:

```auto
bnd print -m */target/*.jar > allmanifests.txt

```

Or this if you have the usual bnd workspace layout with a `generated` folder, containing the jar of your bundle:

```auto
bnd print -m */generated/*.jar > allmanifests.txt

```

This writes all MANIFEST.MF entries to a `allmanifests.txt` for examination.

I also suggest adding the ``-v --verify` ` option to also verify the bundle’s correctness.