[equinox-dev] Survey - Relevance of Open Source Research

2019-12-02 Thread Michelangelo Machado
Dear all, We are conducting a Survey about the Relevance of Open Source Research. This Survey is part of my bachelor's monograph in Computer Science at the University of Brasilia (Brazil), and it is an extension of our first approach aimed only at undergraduate students, which resulted in the foll

Re: [equinox-dev] Should OSGi bundles always export all packages?

2019-12-02 Thread Lars Vogel
Thanks BJ for your advice. Your explanation was also my understanding (see bug discussion) but we had different opinions in the team, hence the request to the OSGi experts. Also thanks to Neil for answering in the bug. On Mon, Dec 2, 2019 at 4:49 PM BJ Hargrave wrote: > > That advice is too br

Re: [equinox-dev] Should OSGi bundles always export all packages?

2019-12-02 Thread Neil Bartlett
The OSGi Specifications do not make any recommendation on this question – that is not their function. But as I have commented in the bug, why would we have to enumerate all exported packages in the Export-Package header if exporting everything was intended to be the default? On Mon, 2 Dec 2019 at

Re: [equinox-dev] Should OSGi bundles always export all packages?

2019-12-02 Thread BJ Hargrave
That advice is too broad. A bundle should export the package which are its API. That is, the packages which users of the bundle need access to in order to use the bundle. Packages which are implementation detail should not be exported to properly encapsulate implementation detail. Some bundles will

[equinox-dev] Should OSGi bundles always export all packages?

2019-12-02 Thread Lars Vogel
Hi OSGi experts, In one of the Eclipse releases a warning was activated that a plugin must exports all its packages. It is possible to change this for a workspace but IMHO this new default is wrong. Plug-ins should not always export all packages as IMHO this defies the purpose of a good module s