Hey! I would like to point out a (from my point of view quite important) problem with removing Code Recommenders from the packages.
If a user opens an existing workspace with an install that does NOT contain the code recommenders plugins, but the workspace got created with an install that contained Code Recommenders, the complete content-assist experience for Java is broken. The user has to reset the content-assist settings manually to make things work again. This is a pretty bad user experience. I expect this to effect basically every single Eclipse Java developer using the new Eclipse 2018-12 release who opens a previously created workspace. The background: It looks like code recommenders disables the regular Java content-assist computers and enables its own. When the workspace is re-used with a new workspace without recommenders, those enabled content-assist computers don’t exist anymore, but the regular Java ones are not re-enabled. I guess I should open a bug for that? Opinions? Cheers, -Martin > Am 11.12.2018 um 21:49 schrieb Marcel Bruch <marcel.br...@codetrails.com>: > > Dear Cross-Projects, > > I‘d like to withdraw Code Recommenders participation from the SimRel and EPP > packages. > > The project committers currently do not have enough resources to keep pace > with the changes in JDT/Java and thus we‘ve to take this necessary and long > due action. > > Best, > Marcel > > Von meinem iPad gesendet > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe from > this list, visit > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
