[
https://issues.apache.org/jira/browse/FELIX-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved FELIX-5191.
----------------------------------------
Resolution: Not A Problem
Just tested it with my project and it works fine. Many thanks.
> Optionally include bnd.bnd files in maven-bundle-plugin
> -------------------------------------------------------
>
> Key: FELIX-5191
> URL: https://issues.apache.org/jira/browse/FELIX-5191
> Project: Felix
> Issue Type: Improvement
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.0.1
> Reporter: Christian Schneider
> Fix For: maven-bundle-plugin-3.0.2
>
>
> From the bndtools community I learned the good practice to move the bnd
> configurations from the pom into a bnd file by including it in the maven
> bundle plugin config (see below) in the parent pom. So all the modules of my
> project do not need the maven-bundle-plugin config in their poms anymore as
> all OSGi settings are done in the bnd file.
> The problem with this approach is that all the modules then must have a
> bnd.bnd file even if they do not want to override anything.
> So the minimum thing I would like to change is to ignore the absence of a bnd
> file that is included.
> Additionally I think it would be nice to have a default of using a bnd.bnd
> file for configuration if it is present. This is just a little syntactic
> sugar of course but I think it would encourage to use the default name
> bnd.bnd for the bnd file.
> If the community is positive about those changes I can submit a patch or
> github pull request.
> ---
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <version>3.0.0</version>
> <extensions>true</extensions>
> <configuration>
> <instructions>
> <_include>bnd.bnd</_include>
> </instructions>
> </configuration>
> </plugin>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
