Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
maven-bundle-plugin-2.3.5
Description
If ${project.build.outputDirectory} includes a resource META-INF/MANIFEST.MF, maven-bundle-plugin uses it, and there is no way to override that behavior. I would like to be able to tell the maven-bundle-plugin to ignore an existing META-INF/MANIFEST.MF or, more generally, any set of manifest resources/files via a <manifestFiles><includes>...</includes><excludes>...</excludes></manifestFiles>. I don't know if this would also require a change to the underlying bnd tool or not, but it seems like it would, because I don't see this feature there, either. I defer to the experts to determine whether bnd needs such an associated enhancement.