Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates
 216.239.58.185 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Gldp1MPz456gYPPTZ8x02tPIMOHEMOz7NySrYgG3CVGAfpAzNwX/DWv6lzQjPRnuX1TBBN4/Zwfd0SO5ya32urf7Rp8HBR2j6ac0u4dvhx437LqzAEAN5+iRLduFvcE56nv6cAapHnizy8u5idGIEyhZAkGnBCUeTfsP9g6fq78=
Message-ID: <25aac9fc0804110825v478cbc01naa86332d12b64229@mail.gmail.com>
Date: Fri, 11 Apr 2008 16:25:54 +0100
From: sebb <sebbaz@gmail.com>
To: general@incubator.apache.org
Subject: Re: UIMA release - lots of missing SVN eol-style property settings
In-Reply-To: <47FF7344.6000200@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <25aac9fc0804101345q319de47av88d370a1dbf84e13@mail.gmail.com>
	 <47FEF70B.4010506@gmx.de>
	 <25aac9fc0804110600x4045346ao369f4f557bf2594f@mail.gmail.com>
	 <47FF7344.6000200@gmx.de>

On 11/04/2008, Thilo Goetz <twgoetz@gmx.de> wrote:
> sebb wrote:
>
> > On 11/04/2008, Thilo Goetz <twgoetz@gmx.de> wrote:
> >
> > > sebb wrote:
> > >
> > >
> > > > The SVN tag
> > > >
> > > >
> > > >
> > >
> https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-05
> > >
> > > > has lots of missing SVN eol-style settings. See the file
> > > >
> > > > uimaj-2.2.2-05.sh
> > > > in
> > > > http://people.apache.org/~sebb/SVNfixes/
> > > >
> > > > This should probably be applied to trunk as well ...
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > >
> > > > To unsubscribe, e-mail:
> > > >
> > > general-unsubscribe@incubator.apache.org
> > >
> > > > For additional commands, e-mail:
> > > >
> > > general-help@incubator.apache.org
> > >  Hi Sebb,
> > >
> > >  thanks for looking over our release.
> > >
> > >  There are a lot of files in your list where not setting
> > >  the eol-style property is intentional: all our test files.
> > >
> >
> > Which extensions are these?
> > I can change my script to treat these differently.
> >
>
>  .txt mostly, some .xml.  So I think one needs to handle this
>  on an individual file level.
>

My script can be set up to allow optional values, e.g. at present pdf
files can have a mime-type of either
   'application/octet-stream'
 or
   'application/pdf'

>
> >
> >
> > >  Setting eol-style:native would make our tests fail on one
> > >  platform or another as they're usually compared to some
> > >  expected output, which in turn depends on the exact byte
> > >  content of the files.
> > >
> > >  Unfortunately, there is no (valid) eol-style:none
> > >  or such that allows us to make this intention explicit.
> > >
> >
> > In which case, the tests may fail to work on OSes with a different
> > line ending, unless you set the mime-type to binary.
> >
>
>  I don't understand that remark.
>
>
> >
> >
> > >  For the java code we could set it to native.  We just never
> > >  felt the need.  Since we need to be careful with our test
> > >  files, we don't follow the automatic eol-style client setup
> > >  as recommended.  AFAIK, all UIMA developers use Eclipse
> > >  for their development, and Eclipse doesn't care about
> > >  eol style (or not that I noticed anyway).
> > >
> >
> > No it doesn't mind. But SVN does.
> > If you edit a Java file on Unix and commit to SVN, then someone who
> > edits it on Mac or Windows and commits to SVN will generate an SVN
> > diff which shows the whole file has been changed. Makes it very
> > difficult to see what has actually changed. Likewise for pom.xml etc.
> >
>
>  True.  We try to avoid that ;-).  Although most of us work on windows,
>  we use unix style eol chars for all source code.
>

That probably annoys the Mac Users...

>
> >
> >
> > >  I hope you'll agree that it's up to the project to set an
> > >  eol-style policy.  Our policy is not to set the property
> > >  unless it's required (e.g., for .sh or .bat files).
> > >
> >
> > Indeed, but see also:
> >
> >
> http://www.apache.org/dev/version-control.html#https-svn-config
> >
> > These conventions are generally used by Java projects, e.g. all of
> Commons.
> >
>
>  Yes, and they don't work for us, as I pointed out earlier.
>
>  There are also settings in there that I find rather doubtful.  What
>  is the point of having eol-style for .bat files set to native?

No idea - I would have thought CRLF would be more appropriate.

>
>  So how do you create a distribution?  To my mind, it shouldn't matter
>  if you extracted the code on linux or windows.  The distribution should
>  come out the same and work on both platforms.
>
>
>  --Thilo
>
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail:
> general-unsubscribe@incubator.apache.org
>  For additional commands, e-mail:
> general-help@incubator.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org