1) it should not break anything; you do not need to have = in property files
2) report a feature request in our jira that we should try and keep the existing value assignment operator (either space or =) when saving
3) Use Open With... to choose another editor.
1) It definitely breaks the resource bundle editor plugin. I know properties files can have the property names and values seperated by a space (and I think a colon if I remember right), but I've never seen anyone NOT use the equals sign. Any reason you've moved to spaces as default?
2) will do! Thanks.
3) yes, that's what I had to do. I actually just changed my file association.
btw. I just tried to reproduce this and when I have
it is kept.
Could you let us know how you reproduce it ?
Which resuorce bundle editor plugin ? It needs to be fixed!
it looks like any other eclipse plugin and if it does not support = it is a bug you should report against them.
But with respect to us you should report it in jira with an example of the properties file before and after as I cannot reproduce it.
Okay, I think I've found the problem. It's not a problem with the Red Hat Properties Editor. Sorry for the false alarm, although I am confused about things now.
Basically, the resource bundle editor creates property files with the following format:
"key = value"
The Red Hat editor, identifies that first space before the = sign as the separator, however it also strips out the = sign and the following space. As an example:
key2 = value2
key3 =value 3
same file after being opened with the Red Hat editor:
key3 value 3
I can see that based on the docs for the Java Properties file class that the editor is doing the correct thing, however even Sun's example on resource bundles uses the " = " syntax:
So I will definitely file a bug with the resource bundle editor, so that it will support the spec better, but I would also like to file a Jira ticket asking that the Red Hat editor preserve the existing separations if they are legal.