Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
maven-bundle-plugin-3.0.1
-
None
Description
In my company it happens sometimes that people using the Maven Bundle Plugin to produce the bundle misinterpret the configuration settings, producing a MANIFEST file with invalid OSGi entries, i.e. given a project with the following structure:
myproject ├── src │ ├── main │ │ ├── java │ │ │ └── org │ │ │ └── apache │ │ │ ├── acme │ │ │ │ ├── utils
and the pom.xml is wrongly configured as:
<plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <extensions>true</extensions> <configuration> <instructions> <Export-Package> nothing </Export-Package> </instructions> </configuration> </plugin>
it makes the Export-Package header resulting as Export-Package: nothing.
A MOJO, invoked during the verify phase, would be very useful to check the target bundle integrity and prevent this kind of wrong exports.
Patch is coming.