You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2003/09/10 19:53:44 UTC
[issues] Updated: (FOR-31) xml output doesn't use the correct line separator
The following issue has been updated:
Updater: Steven Noels (mailto:stevenn@outerthought.org)
Date: Wed, 10 Sep 2003 7:53 PM
Comment:
Unless the *.zip distribution is built on a Windows machine, this problem will remain. A CVS checkout has automatic linefeed conversions applied upon, whereas the dist will depend on the line endings of the local sandbox of the guy building the release. Another option might be to integrate the fixcrlf ant task in the release target.
Changes:
[Version] [HEAD] was added
[Version] [0.3] was removed
[Component] changed from [Core operations] to [shbat distribution - Forrest CLI]
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-31&page=history
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-31
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-31
Summary: xml output doesn't use the correct line separator
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Component: shbat distribution - Forrest CLI
Versions:
HEAD
Assignee:
Reporter: Brill Pappin
Created: Sat, 8 Mar 2003 1:32 AM
Updated: Wed, 10 Sep 2003 7:53 PM
Environment: Windows XP, JDK 1.4.1, Forrest 3.0 (release)
Description:
running "forrest seed" creates the seed site, which works fine... however the output should use the line separator chars from System.getProperty("line.separator").
Currently, you must open and reformat all the documents in an editor that can understand the line separator, before using "native" tools.
It's still usable, but what a pain.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org/jira//Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: [issues] Updated: (FOR-31) xml output doesn't use the correct
line separator
Posted by Steven Noels <st...@outerthought.org>.
Juan Jose Pablos wrote:
> ok, I agree, we should be asuming that *.zip is for windows users, so do
> you think that we should fix crlf for all text files (xml,xsl,svg...)?
Since the aspect of line endings is mostly irrelevant to XML parsing,
I'm -0 on adding fixcrlf to the dist build target. Personally, FOR-31
hardly qualifies as a bug, rather an annoyance. Making proper dists on
proper platforms would be a much better approach at tackling this annoyance.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: [issues] Updated: (FOR-31) xml output doesn't use the correct
line separator
Posted by Juan Jose Pablos <ch...@che-che.com>.
Steven Noels wrote:
> Juan Jose Pablos wrote:
>
> For our own projects, we build a *.tar.gz dist on a Linux machine, and
> the *.zip alternative on a Windows machine. That should be the safest
> and easiest. And since making a dist for Forrest is peanuts (compared
> with Cocoon), I would go for this scheme.
>
ok, I agree, we should be asuming that *.zip is for windows users, so do
you think that we should fix crlf for all text files (xml,xsl,svg...)?
Cheers,
Cheche
Re: [issues] Updated: (FOR-31) xml output doesn't use the correct
line separator
Posted by Steven Noels <st...@outerthought.org>.
Juan Jose Pablos wrote:
> Maybe we need to applied to all text files (xml,xsl,svg) on the *.zip
> distribution.
>
> what do you think?
For our own projects, we build a *.tar.gz dist on a Linux machine, and
the *.zip alternative on a Windows machine. That should be the safest
and easiest. And since making a dist for Forrest is peanuts (compared
with Cocoon), I would go for this scheme.
There's be other platform particularities as well, like the situation
with tar vs gnutar on Mac OS X, or WinZip making a faulty extraction of
a tgz archive... IMHO, it's still better to build a dist for a specific
destination on that destination platform.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source Java & XML An Orixo Member
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: [issues] Updated: (FOR-31) xml output doesn't use the correct
line separator
Posted by Juan Jose Pablos <ch...@che-che.com>.
Steven,
>Another option might be to integrate the fixcrlf ant task in the release target.
I forwarded a patch to resolve this, but I did not applied because I
wanted someone to have a look.As a minimun this patch apply fixcrlf to
the freshsite.
Maybe we need to applied to all text files (xml,xsl,svg) on the *.zip
distribution.
what do you think?
Cheers,
Cheche