From my point of view the arguments for and against the bnd file
extraction.
Pro:
- You typically do not need a plugin definition at all in each module
pom. So the definition just in the bnd file is much more concise.
- If you use bndtools you get a nice view and editor for the bnd file.
This is not so important for me though.
Con:
- If you use intellij then most probably you will have some completion
support for the configurations in the pom but not for the bnd.bnd file
So I think the extraction is best for users of eclipse and bndtools and
less valuable for other IDEs. To be honest though editing the bnd files
is not really a big deal.
I typically only use Import-Package, Export-Package, Private-Package and
Bundle-Activator and these four I can type without completion. The maven
bundle plugin also nicely
complains if you have any errors in the file. So I think editing with a
simple text editor is no big deal.
Christan
On 12.02.2016 10:54, Markus Rathgeb wrote:
Hi Christian,
thank you for your answer.
I want to state, that there are no feelings from my side what is better.
I want to collect the technical details for further decisions on the
projects I maintain.
So, let's assume I do not use the configuration in a parent project
(just add maven-bundle-plugin to the used plugins and set
extensions=true) and also not use properties, the bnd.bnd file will
result in less lines in the pom if I want to change the default
configuration of the plugin.
Are there other pros?
Best regards,
Markus
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
