- This topic has 3 replies, 4 voices, and was last updated 12 years, 1 month ago by support-swapna.
-
AuthorPosts
-
Will SchneiderMember*** Date:
Thursday, July 22, 2010 9:12:14 AM EDT** System properties:
OS=Linux
OS version=2.6.32
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 8.5
Build id: 8.5-20100319*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 8.5
Build id: 8.5-20100319Eclipse startup command=-os
linux
-ws
gtk
-arch
x86
-showsplash
-launcher
/home/will/Genuitec/MyEclipse 8.5/myeclipse
-name
Myeclipse
–launcher.library
/home/will/Genuitec/MyEclipse 8.5//../Common/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.200.v20090520/eclipse_1206.so
-startup
/home/will/Genuitec/MyEclipse 8.5//../Common/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-exitdata
1b0018
-install
/home/will/Genuitec/MyEclipse 8.5
-configuration
/home/will/Genuitec/MyEclipse 8.5/configuration
-vm
/home/will/Genuitec/Common/binary/com.sun.java.jdk.linux.x86_1.6.0.013/bin/java+ = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + = + =
I have a number of properties files that have extra ‘\’ characters added on save, e.g.
“following credits:\n” becomes “following credits\:\n”When I switch to the Eclipse Properties File editor these extra ‘\’ characters are not added on save.
Note the extra and unwanted ‘\’ before the colon (‘:’)
If I use the regular Eclipse properties file editor this behavior does not happen.
support-shaliniMemberwfschneider,
I could replicate this at my end. I have raised a PR with the dev team.
Thank you for bringing this up.
SmittyParticipantHas this issue been fixed yet and if so which version was it fixed in? We have some developers on version 8.6 and this is still occuring. Seems in some cases it adds the backslash to escape characters and in other cases where we have a regular expression it’s removing the 3rd and 4th backslash from the expression:
(\w|@|$|\!|%|\#)+.
support-swapnaModeratorsmitty_in_vancouver,
We already have a PR filed for this issue, but due to several other higher priority issues, this is still not fixed. I have escalated it to the dev team to look into it.
Sorry for inconvenience caused.
-
AuthorPosts