Bug 464774 - "Enable Code Recommenders code completion" cannot be stored when Oomph is installed
Summary: "Enable Code Recommenders code completion" cannot be stored when Oomph is ins...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Recommenders (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Andreas Sewe CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 464777
Blocks:
  Show dependency tree
 
Reported: 2015-04-16 06:03 EDT by Andreas Sewe CLA
Modified: 2019-07-24 14:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Sewe CLA 2015-04-16 06:03:36 EDT
To reproduce:

- Use a fresh Eclipse install containing Eclipse Oomph, e.g., based on the Eclipse Mars M6 package for Java Developers.

- Install the latest development version of Code Recommenders for Java Developers from [1].

- Go to the Code Recommenders > Completions preference page and click on "Enable Code Recommenders code completion".

- Close the preferences.

- Oomph will now ask you whether to record this preference change. Agree.

This causes an error dialog to appear, with the following information:

An internal error occurred during: "Store preferences".
An invalid XML character (Unicode: 0x0) was found in the element content:org.eclipse.jdt.ui.textProposalCategory
Comment 1 Andreas Sewe CLA 2015-04-16 06:05:22 EDT
*sigh* Apparently, I cannot copy and paste the full error message into Bugzilla, as it contains '\0' characters itself.
Comment 2 Andreas Sewe CLA 2015-04-16 06:14:01 EDT
(In reply to Andreas Sewe from comment #1)
> *sigh* Apparently, I cannot copy and paste the full error message into
> Bugzilla, as it contains '\0' characters itself.

Bug 464777 contains the full details. (AFAICT, this is really a bug in Oomph, not Code Recommenders.)
Comment 3 Andreas Sewe CLA 2015-04-17 11:12:12 EDT
(In reply to Andreas Sewe from comment #2)
> Bug 464777 contains the full details. (AFAICT, this is really a bug in
> Oomph, not Code Recommenders.)

I can confirm that, with the latest version of Oomph (1.1.0 build 1119), this doesn't occur anymore. Thanks, Eike.