| Setting "Default encoding" property in "Content Types" fails [message #1711109] |
Tue, 13 October 2015 06:37  |
 Johan Ek
Messages: 4
Registered: October 2015 |
Junior Member |
|
|
Hello,
First of all, let me thank you for a really nice way to customize and create eclipse packages! I can't believe that this hasn't been more Hyped 
Still a lot to learn though and the documentation can be hard to find...
I am currently creating a eclipse setup for the team I'm in. Everything seems to be working well.
Before, we used Workspace mechanics to share preferences and it was very convinient to import those preferences to our oomph setup.
However, one perculiar property refuses to be set, In Preferences -> General -> Content Types we want to set groovy source file:s default encoding to UTF-8.
We have the following property node in oomph:
Key: /instance/org.eclipse.core.runtime/content-types/org.eclipse.jdt.groovy.core.groovySource/charset
Value: UTF-8
When running the setup, it creates the property correctly in metadata, but the default encoding is emtpy. If i remove the property from the settings file, and manually enters the encoding in preferences, the same property shows up in the settings file.
To actually set the value, one has to press the button "update" next to the Default encoding field in preferences.
Could this be the problem? Is there anything more I need to do in order to get that property set in my setup?
Anyone having faced this or have an idea?
Regards
Johan
|
|
|
| Re: Setting "Default encoding" property in "Content Types" fails [message #1711162 is a reply to message #1711109] |
Tue, 13 October 2015 15:41  |
Ed Merks
Messages: 33258
Registered: July 2009 |
Senior Member |
|
|
Johan,
Yes, it sounds like perhaps more action is needed than simply putting
the value into the preference. Investigation is required. Please open a
bugzilla to track the progress. It's hard to get that update button to
enable.
With respect to this encoding preference, it strikes me that UTF-8 is a
good general default for the whole workspace...
On 13/10/2015 3:06 PM, Johan Ek wrote:
> Hello,
>
> First of all, let me thank you for a really nice way to customize and
> create eclipse packages! I can't believe that this hasn't been more
> Hyped :) Still a lot to learn though and the documentation can be hard
> to find...
>
> I am currently creating a eclipse setup for the team I'm in.
> Everything seems to be working well. Before, we used Workspace
> mechanics to share preferences and it was very convinient to import
> those preferences to our oomph setup.
>
> However, one perculiar property refuses to be set, In Preferences ->
> General -> Content Types we want to set groovy source file:s default
> encoding to UTF-8.
>
> We have the following property node in oomph:
> Key:
> /instance/org.eclipse.core.runtime/content-types/org.eclipse.jdt.groovy.core.groovySource/charset
> Value: UTF-8
>
> When running the setup, it creates the property correctly in metadata,
> but the default encoding is emtpy. If i remove the property from the
> settings file, and manually enters the encoding in preferences, the
> same property shows up in the settings file.
> To actually set the value, one has to press the button "update" next
> to the Default encoding field in preferences.
> Could this be the problem? Is there anything more I need to do in
> order to get that property set in my setup?
>
> Anyone having faced this or have an idea?
>
> Regards
> Johan
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.03702 seconds
] 
Search
Help
Register
Login
Home
