Yeah, this is what we do in Beehive as well. My suggestion would be to document the SVN configuration settings for OpenJPA committers in something like DEVELOPING.txt at the top-level of the project. Over time as new committers come on board, just make sure that they're aware of this and use it in their environments.
Eventually you'll reach a stable state where most commits are correct and then just do what Dain said -- fix the eol-style across the depot. Our instructions are here: http://svn.apache.org/repos/asf/beehive/trunk/DEVELOPING.txt Eddie On 2/1/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:
About once a quarter in the Geronimo project, someone writes a script to fix all of the properties in the tree. This is because people normally forget to set these properties, or their IDE doesn't apply them. It would be nice if there were a cron job to update the properties once a week. -dain On Feb 1, 2007, at 12:59 PM, Patrick Linskey wrote: > So for OpenJPA, the [auto-props] section should include the > following as > well: > > *.java: svn:eol-style=LF > *.properties: svn:eol-style=LF > *.xml: svn:eol-style=LF > > I haven't tried this out yet, but TFM claims that those are the > correct > values. Sadly, as far as I can tell, this cannot be used to disable > the > svn:executable setting that svn slaps on files added via Windows. > > -Patrick > > -- > Patrick Linskey > BEA Systems, Inc. > > ______________________________________________________________________ > _ > Notice: This email message, together with any attachments, may > contain > information of BEA Systems, Inc., its subsidiaries and > affiliated > entities, that may be confidential, proprietary, copyrighted > and/or > legally privileged, and is intended solely for the use of the > individual > or entity named in this message. If you are not the intended > recipient, > and have received this message in error, please immediately return > this > by email and then delete it. > >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >> Sent: Thursday, February 01, 2007 12:02 PM >> To: open-jpa-dev@incubator.apache.org >> Subject: Eol-style >> >> This just in: >> >> >>> If I have to do it individually to files, is there some way >> to ensure that >>> any text file checked it gets this property set? Otherwise, >> we're bound to >>> forget to set it frequently. >> >> Yes, it's a new feature in your ~/.subversion/config file, not yet >> documented in the Book. Enable the "auto-props" feature and set >> patterns accordingly. Any time you 'svn add' a text file, it will >> automatically set properties for you. Here's the excerpt from >> a modern >> ~/.subversion/config file: >> >> ### Set enable-auto-props to 'yes' to enable automatic properties >> ### for 'svn add' and 'svn import', it defaults to 'no'. >> ### Automatic properties are defined in the section 'auto-props'. >> enable-auto-props = yes >> >> >> >> >> ### Section for configuring automatic properties. >> ### The format of the entries is: >> ### file-name-pattern = propname[=value][;propname[=value]...] >> ### The file-name-pattern can contain * as wildcard. All entries >> ### which match will be applied to the file. >> [auto-props] >> *.c = svn:eol-style=native >> *.cpp = svn:eol-style=native >> *.h = svn:eol-style=native >> *.dsp = svn:eol-style=CRLF >> *.dsw = svn:eol-style=CRLF >> *.sh = svn:eol-style=native;svn:executable >> *.txt = svn:eol-style=native >> *.png = svn:mimetype=image/png >> *.jpg = svn:mimetype=image/jpeg >> Makefile = svn:eol-style=native >> >> >> Craig Russell >> >> Architect, Sun Java Enterprise System http://java.sun.com/products/ >> jdo >> >> 408 276-5638 mailto:[EMAIL PROTECTED] >> >> P.S. A good JDO? O, Gasp! >> >> >>
