[
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?
|
From what I understand, the point of the rule is "
allowing experimentation and investigation".The major version number must only change when changing "real" APIs (non-internal).
Adopters can experiment with non-APIs, knowing they can (and will) be broken by any release.
On Wed, Feb 2, 2011 at 9:30 AM, Eike Stepper
<stepper@xxxxxxxxxx> wrote:
Am 02.02.2011 09:24, schrieb Daniel Megert:
Thank you, Dani. That may be what I was looking for.
But it does not explain the difference between or consequences of:
a) exporting a non-API package as x-internal
b) not exporting it at all
I understand that some users want to extend everything but I assume the directive is not "make everything public" because then I would aks what is the minor version segment good for. If everything is public API then almost every change to anything would break binary compatibility and force a major version increase. Maintenance would be almost impossible, too.
--
Nicolas Bros
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxxnbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com.: model driven agility :.