Hi, Just wanted to point out the auto-props feature in the svn client config file (at a glance it seems no one else has):
http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.4 I use it to ensure that all text files have svn:eol-style set to native - instead of relying on Subversion's "guesswork" when I add files to version control :) Here are my settings: [miscellany] enable-auto-props = yes [auto-props] *.java = svn:eol-style=native *.xml = svn:eol-style=native *.wsdd = svn:eol-style=native *.wsdl = svn:eol-style=native *.properties = svn:eol-style=native *.txt = svn:eol-style=native *.vm = svn:eol-style=native *.htm = svn:eol-style=native *.html = svn:eol-style=native *.js = svn:eol-style=native *.css = svn:eol-style=native *.sh = svn:eol-style=native *.bat = svn:eol-style=native *.conf = svn:eol-style=native cheers, Marinó -----Original Message----- From: Nathan Bubna [mailto:[EMAIL PROTECTED] Sent: 15. október 2005 18:30 To: Velocity Developers List Subject: Re: eol-style On 10/14/05, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Hi Henning, > > Actually, this still doesn't work for ParserTokenManager (setting > eol-style to native). It appears that the line endings are > inconsistent (when javacc is run on Windows). Probably similar to the > earlier Anakia problem (which we fixed). > > svn: File 'C:/Documents and Settings/wglass/My > Documents/GAWE/velocity/trunk/src/java/org/apache/velocity/runtime/parser/Pa rserTokenManager.java' > has inconsistent newlines > > The solution for me is to open and close in Textpad, which has an > option for force PC style newlines. nice tip. Textpad rocks. > WILL > > ----- Original Message ----- > From: "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> > Newsgroups: hometree.jakarta.velocity.dev > To: <velocity-dev@jakarta.apache.org> > Sent: Friday, October 07, 2005 2:04 AM > Subject: Re: svn commit: r306522 - in /jakarta/velocity/core/trunk: > src/java/org/apache/velocity/runtime/parser/ test/templates/ > test/templates/compare/ > > > > "Will Glass-Husain" <[EMAIL PROTECTED]> writes: > > > >>3) If necessary, convert the line endings for > >>ParserTokenManager.java to your native platform (other files are ok > >>- for some reason this is always Unix). > > > > You shouldn't have to do this. As the eol-style is part of the > > Subversion meta-information, it will be converted automatically, > > once you check your changes in. Just do a "svn up" after checking > > in, it should work. > > > > The Java platform itself should not care about the line endings when > > compiling on Windows. > > > > Best regards > > Henning > > > > -- > > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH > > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/ > > > > RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire > > Linux, Java, perl, Solaris -- Consulting, Training, Development > > > > 4 - 8 - 15 - 16 - 23 - 42 > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
