[
https://issues.apache.org/jira/browse/FELIX-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288807#comment-15288807
]
Julian Sedding commented on FELIX-5258:
---------------------------------------
In the case of an error, a link to
http://bnd.bndtools.org/heads/export_package.html might be helpful to guide the
developer to the documentation for the {{Export-Package}} header.
> Add a new MOJO which verifies the bundle integrity
> --------------------------------------------------
>
> Key: FELIX-5258
> URL: https://issues.apache.org/jira/browse/FELIX-5258
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.0.1
> Reporter: Simone Tripodi
> Assignee: Carsten Ziegeler
> Fix For: maven-bundle-plugin-3.1.0
>
> Attachments: FELIX-5258.patch, FELIX-5258.patch.1
>
>
> 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:
> {noformat}
> myproject
> ├── src
> │ ├── main
> │ │ ├── java
> │ │ │ └── org
> │ │ │ └── apache
> │ │ │ ├── acme
> │ │ │ │ ├── utils
> {noformat}
> and the {{pom.xml}} is wrongly configured as:
> {noformat}
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <extensions>true</extensions>
> <configuration>
> <instructions>
> <Export-Package>
> nothing
> </Export-Package>
> </instructions>
> </configuration>
> </plugin>
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
