Rather than using the archive format to determine the linebreak
convention, I would prefer an explicit build option (build for CR or
build for CR/LF). Also, having Windows specific archive(s) might imply
that there is more OS-specific behavior than we really have...
All of our previous Milestone distributions have used CR's only, has this posed a problem to Windows users? It hasn't really been a problem for me developing on a Windows platform... I wonder if Geronimo users would be happy with CR-only distributions until we're ready to offer truly integrated Windows-specific behavior...
On 12/1/05, John Sisson <firstname.lastname@example.org> wrote:
Currently if you build a Geronimo distribution on Windows, and install
on a *NIX platform, files such XML and property files will contain
This is ugly if you are attempting to edit an XML plan using something
like the vi editor that displays the carriage returns as ^M.
This also is a problem for the viewable files in the root directory of
the install, such as the README.txt file.
We could fix this by using the fixcrlf task (in the same place I did for
GERONIMO-1232) and making the assumption that the zip distribution will
only be used on Windows and the tar.gz distributions only used on *NIX
platforms. This would allow people to use native editors on their
platform (e.g. vi or notepad on windows) without having any problems.
Is this a reasonable assumption to make? Of course we could explicitly
state on the download page what the difference between the distributions
Here is an example of me trying to edit an XML file using vi on Solaris
(when built from Windows):
<?xml version="1.0" encoding="UTF-8"?>^M
Copyright 2004 The Apache Software Foundation^M
Licensed under the Apache License, Version 2.0 (the "License");^M
you may not use this file except in compliance with the License.^M
You may obtain a copy of the License at^M
Unless required by applicable law or agreed to in writing, software^M
distributed under the License is distributed on an "AS IS" BASIS,^M
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
See the License for the specific language governing permissions and^M
limitations under the License.^M
<!-- $Rev: 292333 $ $Date: 2005-09-29 08:09:15 +1000 (Thu, 29 Sep 2005)
A security realm available to be used by sample applications.^M