For me personally IDE support is irrelevant. BND is a command like tool and while support for it in IDEs is different at the end of the day all you need is a properties file editor. You don't get code competition for POMs neither so there is absolutely no difference (in terms of amount of work needed) where you put your instructions. But on the Pro side I would put
- standard: bnd.bnd is the standard way to configure BND. I just like to use the right tool for the job. For example, consider if you were using some "next generation" build tool that runs Maven under the hood, would you like to have maven configuration in that other fancy tool's config files or rather stick with maven poms? - learning curve: The BND docs have examples how to configure things in bnd.bnd file and it's not always immediately obvious how to transfer those to maven plugin configuration. - plugin independent configuration - obviously bnd-maven-plugin comes to mind first but in general if someone comes with better (in whatever sense) plugin in the future the configuration does not need to change For the record (in case you find some public evidence of me arguing the opposite) some time ago I was totally against using bnd.bnd files. After being kind of forced to do it for a while, I realized it doesn't really make any difference in the effort that it takes to maintain those and at the same time provides clearer separation of concerns. So I changed my mind :) ! Best, Milen On Fri, Feb 12, 2016 at 11:05 AM, Christian Schneider < ch...@die-schneider.net> wrote: > 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 > > -- http://about.me/milen
