-
1. Re: Property File Editor strips out
maxandersen Aug 20, 2007 4:31 AM (in response to modoc)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. -
2. Re: Property File Editor strips out
modoc Aug 20, 2007 4:44 AM (in response to modoc)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. -
3. Re: Property File Editor strips out
maxandersen Aug 20, 2007 4:48 AM (in response to modoc)btw. I just tried to reproduce this and when I have
value=somekey
it is kept.
Could you let us know how you reproduce it ? -
4. Re: Property File Editor strips out
maxandersen Aug 20, 2007 4:59 AM (in response to modoc)Which resuorce bundle editor plugin ? It needs to be fixed!
-
5. Re: Property File Editor strips out
modoc Aug 20, 2007 11:38 AM (in response to modoc)This is the plugin that I use:
http://www.resourcebundleeditor.com/
It may be specific of OS X? I can reproduce it any time I open a properties file with the Red Hat editor. -
6. Re: Property File Editor strips out
maxandersen Aug 20, 2007 1:53 PM (in response to modoc)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. -
7. Re: Property File Editor strips out
modoc Aug 20, 2007 2:15 PM (in response to modoc)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:
test.properties:
key=value
key2 = value2
key3 =value 3
same file after being opened with the Red Hat editor:
key=value
key2 value2
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:
http://java.sun.com/docs/books/tutorial/i18n/resbundle/propfile.html
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.
Sound reasonable?
Devon -
8. Re: Property File Editor strips out
modoc Aug 20, 2007 2:49 PM (in response to modoc)Bug opened with the resource bundle editor here:
http://sourceforge.net/tracker/index.php?func=detail&atid=701316&aid=1777814&group_id=125041 -
-
10. Re: Property File Editor strips out
maxandersen Aug 21, 2007 3:00 AM (in response to modoc)thanks!