[jdom-interest] I just pulled down the latest source via WINC VS

Peter V. Gadjokov pvg at c-c-s.com
Fri Sep 15 16:03:15 PDT 2000

Maybe I'm not quite understanding the original problem, but is fixcrlf
really needed? Id mofifies files checked into the repository at build-time,
which is unusual and unexpected, usually.  Doesn't checking in a build.bat
and a build.sh as binary with the correct line endings take care of this? I
noticed tomcat has a similar directive so there is probably some reason for
doing this I'm missing.

-----Original Message-----
From: Jason Hunter [mailto:jhunter at collab.net]
Sent: Friday, September 15, 2000 11:51 AM
To: Sean Shanny
Cc: jdom-interest at jdom.org
Subject: Re: [jdom-interest] I just pulled down the latest source via

> I have figured this out.  I have my cvs client set up to check 
> things out read-only. The new directives in the build.xml file 
> that fix crlf stuff obviously won't work if
> the file is read-only.  Little gotcha there.

Makes sense.  I think we need a "make dist" target that makes a
distribution and that's the target that should have the fixcrlf.  It's
only when the code might leave your machine that you need to worry about
such things.

To control your jdom-interest membership:

More information about the jdom-interest mailing list