Bob Paulin commented on TIKA-2941:
Just an update to provide some transparency around the "why" we got here. With the newer version of the maven-bundle-plugin when I revert my commit from before I do not see the transitive dependencies included if the tika-parsers are in provided scope. With tika-parsers being embedded it does not really make sense for it to be in provided scope anyways. However with tika-parsers as a compile time dependency all the transitive dependencies are included in maven which is what is being called out as the issue in this JIRA. The good thing from an OSGi perspective we're still OK since only the following packages are exported:
But the maven side still shows all the transitive dependencies coming through. So in an OSGi runtime all these packages are private as expected but in the development environment this is a bit confusing since maven shows them coming through. Will need some time to see if we can get the maven side of this equation right without breaking the OSGi side. Hopefully this helps provide some context around the problem we're solving.