BTW if nobody disagree, I'd like to follow the suggestion I made in the last
message of the linked thread.
In other words, use
http://subversion.apache.org/docs/release-notes/1.8.html#repos-dictated-config
http://blogs.collab.net/subversion/the-road-to-repository-dictated-configuration-day-2-autoprops
Then this problem would be over. No longer need to check from time to time that
concerned files, have svn:eol-style=native property set
This imply that all OFBiz users use svn > 1.7, but we can inform them, et voilà
Opinions?
Jacques
Le 27/07/2016 à 10:50, Jacques Le Roux a écrit :
It's not a workaround, it's how things should work according to Apache
Subversion documentation, but I missed one part.
I was there before, see http://markmail.org/message/fnvmt4fapgowtaux
So please wait I also need to set the svn:properties of the *.gradle files and
commit them in the repo
Jacques
Le 27/07/2016 à 10:25, Taher Alkhateeb a écrit :
Hi Jacques and All,
I noticed in your commit r1754071 you mentioned a workaround for the EOL
issue generated from your editor which I cannot understand. Right now I'm
trying to commit some work for cleaning up the libraries and again I face
the EOL issue (I updated my config file for subversion). What exactly
should I do here?
Regards,
Taher Alkhateeb
