Replace osgi.bnd by inline instructions in POM [PAXSB-71]

[ops4j-issues]

Harald Wellmann created PAXSB-71

---

Affects: 1.6.0 Fixed in: 1.7.0 Votes: 0, Watches: 3

[ops4j-issues]

Toni Menzel commented

Hey Harald,
whats the reasoning for removing the osgi.bnd?

[ops4j-issues]

Harald Wellmann commented

• DRY: common stuff can be factored out into the parent POM.
• Some of the contents don't seem to be well maintained - I think in most cases the defaults calculated by maven-bundle-plugin are more accurate.
• I was under the impression (maybe incorrectly) that POM configuration is now the preferred approach, e.g. Pax Web made the same move a while ago.

[ops4j-issues]

Achim Nierbeck commented

For Pax-Web it's the same, DRY and personal preference to only have one file to contain the whole truth :smile: not two different.
Since using the maven-bundle plugin and beeing dependent on maven I don't think it's worth to keep the bnd instructions in a separate file.

[ops4j-issues]

Toni Menzel commented

I'm totally with anything that makes build instructions more DRY ..
Though there are reasons why bnd instructions may be separated:

• BNDTools work great with maven bundle plugin (you even can use the editor out of the box). But only when .bnd file is separated.
• BNDLib for better or worse is much more than what is currently visibile when using m-b-p.
  With BNDTools we are currently working on a solution to replace m-b-p with a more "native" bnd solution similar to tycho (aka: manifest/bnd first). This would make Maven only a tooling adapter and all OSGi greatness is resolved using OSGi's capability&requirement abstraction (rather than GAV).

Until time has come i am of cause fine with optimizations to reduce duplicacy.