converts bouncycastle OSGi dep from Import-Bundle to Import-Package

[adagios]

Another attempt at resolving #255

Import-Bundle is generally discouraged by OSGi best practices.

See http://stackoverflow.com/questions/1865819/when-should-i-use-import-package-and-when-should-i-use-require-bundle for more info.

[hierynomus]

You've forgotten com.hierynomus.sshj ;)

@15knots does it work for you too?

[adagios]

I wrote on the original bug:

With regards to exporting com.hierynomus.sshj packages, is it something that clients should use directly? I looked and they seemed like internal classes, so I left them out of the Export-Package.

should I add it?

[hierynomus]

Yes, you'd need them if you want to customize the config to use specific algorithms only

[adagios]

done!

[hierynomus]

OSGI n00b question: Should we then not also add a negative Import-Package rule for com.hierynomus.sshj?

[adagios]

All exported packages are normally also imported to prevent multiple class spaces.

See http://blog.osgi.org/2007/04/importance-of-exporting-nd-importing.html for a thorough explanation .