0

I'm struggling to find a reasonable approach to manage a big enough code base, more specifically, how to manage import statements for any given bundle.

The problem is, if you have a bundle with has his own dependencies to other 3rd party libraries, and if you choose to embed some of them (in my case I do), the maven-bundle-plugin will also scan packages from those libraries and add them as imported by your bundle (which is completely counter-intuitive).

A work around my be to get rid of the wildcard * in your import statements, but this means that now you have to maintain the list of imports by hand.

So how do you guys manage this problem ? Am I missing something here ?

Any advice will be greatly appreciated

isco
  • 350
  • 4
  • 15

1 Answers1

2

Bundling a non OSGi third party library is sometimes difficult. The maven-bundle-plugin does a good job in general by only embedding and importing what it finds as being used.

The problem is that many libaries have a lot of dependencies and especially a lot of optional dependencies. In these cases the maven bundle plugin often is careful and imports more than necessary. If you are sure someting is not needed you can forbid the import by specifiying:

Import-Packages: !somepackage, *.

My personal approach of this is to try to avoid libraries with a lot of external dependencies. If I can not avoid them then I check at servicemix bundles where many libaries are already bundled.

Christian Schneider
  • 19,420
  • 2
  • 39
  • 64
  • That would be ideal, except when you want to embed some library, then the wildcard * tells the maven-bundle-plugin to also add packages coming from that library – isco Jun 01 '17 at 11:13
  • So there is no solution to my previous comment (embedding libraries ) ? – isco Jun 08 '17 at 09:54
  • Can you maybe also export those packages? – Christian Schneider Jun 10 '17 at 11:52
  • 1
    Yes, but you end up doing a lot of manual work that should not be necessary, I think the root of the problem is the maven-bundle-plugin, I really don't know why it generates import statements coming from embedded dependencies – isco Jun 14 '17 at 11:52
  • I think by default the plugin generates import and export statements for all contents of the bundle. If you want to avoid that you need to declare the package as private. – Christian Schneider Jun 14 '17 at 13:08
  • 1
    But I have no control over the visibility of those packages as they come from 3rd party libraries – isco Jun 19 '17 at 09:24