Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Is exporting all packages a best practice?

Am 02.02.2011 09:43, schrieb Nicolas Bros:
>From what I understand, the point of the rule is "allowing experimentation and investigation".
The major version number must only change
I disagree with "only". I'm free to increase the major version number whenever I feel it's adequate, for example if the behaviour changes majorly although the API is not impacted at all.

when changing "real" APIs (non-internal).

Adopters can experiment with non-APIs, knowing they can (and will) be broken by any release.
Okay, I finally created two test bundles to simulate both access to not-exported code and to x-internally-exported code. You are right (and I was not aware of that): At OSGi runtime it's not possible to access not-exported code. That's a good argument for exporting everything and marking the "unreal" API x-internal.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper





Attachment: NoExportTest.zip
Description: Zip compressed data


Back to the top