We cannot do this at apache, because the SVN is shared for all projects with 
different requirements, so we use a check in the builds. This check also helps 
to find files you missed to svn add and such stuff.

You can check your own working copy with:
trunk $> ant check-svn-working-copy

This will report files without props, files that are not yet added (unversioned 
ones) and similar stuff.

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -----Original Message-----
> From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of
> Dawid Weiss
> Sent: Wednesday, September 05, 2012 2:25 PM
> To: dev@lucene.apache.org
> Subject: Re: [JENKINS] Lucene-Solr-4.x-Windows (32bit/jdk1.6.0_35) - Build #
> 624 - Still Failing!
> 
> http://stackoverflow.com/questions/2127429/can-i-make-git-svn-handle-
> svneol-style
> 
> Seems to be doable, I'll take a look. It should be an svn commit hook though,
> not a build time check?
> 
> D.
> 
> On Wed, Sep 5, 2012 at 2:17 PM, Robert Muir <rcm...@gmail.com> wrote:
> > On Wed, Sep 5, 2012 at 8:14 AM, Dawid Weiss <dwe...@apache.org> wrote:
> >>> C:\Jenkins\workspace\Lucene-Solr-4.x-Windows\extra-targets.xml:110: The
> following files are missing svn:eol-style (or binary svn:mime-type):
> >>
> >> This prevents people from using alternate workflows (not using svn
> >> but git-svn for example). Can we not check svn properties but the
> >> contents instead? I know svn but I'd rather not use it.
> >>
> >
> > its really necessary or it makes for huge problems with people using
> > windows vs. linux and so on.
> > personally I was tired of fixing this stuff before releases, so we
> > worked on a checker.
> >
> > can you not configure your git-svn or whatever to add eol-style here?
> > surely it has a configuration
> > somewhere, for e.g. *.java. if not then its a bug in git.
> >
> > I did this by adding:
> >
> > *.sha1 = svn:eol-style=native
> >
> > to my ~/.subversion/config
> >
> >
> > --
> > lucidworks.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For
> > additional commands, e-mail: dev-h...@lucene.apache.org
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional
> commands, e-mail: dev-h...@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to