Re: [lsp4e-dev] API Compatibility?

[Mickael Istria <mistria@xxxxxxxxxx>]

On Thu, May 18, 2017 at 9:21 PM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Just note that as opposed to Platform, I'd like LSP4E to try to have a policy to export as minimal things as possible, even if they are marked as internal. I believe for such a relatively simple project, it would encourage more people to contribute directly to LSP4E whereas exposing internals would let people work on extensions on their side too easily when they could contribute to the project directly, or at least be forced to share their use-cases to encourage LSP4E to open up more APIs.

On request of https://bugs.eclipse.org/bugs/show_bug.cgi?id=516975 , the strategy will be to export internal packages in next release (current ones + potential additions on-demand).
But I'd like every adopter of LSP4E to really consider adopting the Generic Editor and to contribute to it if necessary; I wouldn't sleep well if LSP4E becomes another project encouraging the famous "Tragedy of Commons". So, LSP4E stakeholders, please consider contributing to the story of Text Editor in Eclipse IDE as a whole and don't focus only on LSP4E ;)