beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Feit <>
Subject RE: EOL situation with jar files on initial checkout
Date Sun, 18 Jul 2004 16:40:54 GMT
Strange -- I just did a sync from svn within Cygwin, then compared 
junit.jar to the one in my working build -- they're the same.  I'll try to 
do an actual  build in Cygwin, but I don't understand what's different at 
this point...

At 10:10 AM 7/18/2004, Karr, David wrote:
> > -----Original Message-----
> > From: Ken Tam []
> >
> > Strange.  I assume you are talking about the junit.jar in
> > external/junit?  That file has the svn:mime-type property set
> > to application/octet-stream, so svn should be treating it as
> > a binary file and not doing any EOL translation.  I just
> > tried creating a working copy when under Cygwin, and the copy
> > of junit.jar that is brought down is identical (non-corrupt)
> > to the one in my cmd-based working copy.
> >
> > What happens if you don't use Cygwin?
>I tend to think Cygwin wouldn't have anything to do with it, as none of
>the executables involved are Cygwin-built executables.
> > Have you modified your Subversion configuration re: auto-prop
> > and eol handling as described in DEVELOPING.txt?  If not, try
> > that.. the way the docs read, those settings should only
> > matter when adding/committing to the respository, but perhaps
> > we're missing something.
>No, I did not do that.  I figured I should follow the instructions :) .
>If everyone set those properties before they did anything, then perhaps
>that might be the problem.
>After I set those properties, what should I do?  Will "update" reread
>those files, or will I need to re-checkout the module?
> > -----Original Message-----
> > From: Karr, David []
> >
> > My platform is Cygwin on XP.
> >
> > I was able to do the initial checkout, but I had problems on
> > the build. The first problem I hit was problems interpreting
> > the "junit.jar" file. I inspected the contents with "od -h",
> > and I saw that it had been corrupted with EOL translation.  I
> > haven't changed any settings for eol translation.  The
> > BUILDING.txt file doesn't indicate this.  Should it?

View raw message