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?

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.


Cheers
/Eike

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


Dani


From:
Eike Stepper<stepper@xxxxxxxxxx>
To:
Cross project issues<cross-project-issues-dev@xxxxxxxxxxx>
Date:
02.02.2011 09:20
Subject:
[cross-project-issues-dev] Is exporting all packages a best     practice?



Hi,

Sorry if this is off-topic but I don't know a better place to ask.

One of my committers asked me why he's forced (through the rigide warning
settings I dictate per IProject) to explicitely export all packages from a
bundle, including those that are then marked x-internal. I vaguely recall
that this has been discussed before and that there was an explanation, but
I simply can't find it anymore. For example, is it true, that the
x-internal attribute is not recognized by non-Equinox OSGis?

Cheers
/Eike

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


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Nicolas Bros
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxx
nbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com
.: model driven agility :.

Back to the top