You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2006/08/29 03:30:24 UTC

[jira] Updated: (FOR-925) Windows adds ^M to every line of generated *.css files when publishing site.

     [ http://issues.apache.org/jira/browse/FOR-925?page=all ]

David Crossley updated FOR-925:
-------------------------------

          Component/s: Core operations
                       Launch 'forrest'
                           (was: Tool: Forrestbot)
        Fix Version/s:     (was: 0.8-dev)
    Affects Version/s: 0.7

Here is some email discussion
http://marc.theaimsgroup.com/?t=115606165300001
and some other threads around that time.

We are not sure what causes this. It might be related to Chaperon - it processes some CSS files looking for links. Or it might be the Cocoon Text Serializer.

The workaround is after Cocoon has finished, then process all CSS files using Ant's "fixcrlf".

> Windows adds ^M to every line of generated *.css files when publishing site.
> ----------------------------------------------------------------------------
>
>                 Key: FOR-925
>                 URL: http://issues.apache.org/jira/browse/FOR-925
>             Project: Forrest
>          Issue Type: Bug
>          Components: Launch 'forrest', Documentation and website, Core operations
>    Affects Versions: 0.7, 0.8-dev
>            Reporter: Gavin
>
> When using forrest -f publish.xml build , windows adds a ^M (CR-LF) to every line of every generated *.css file.
> The source css files are good, but look at /site-author/build/forrest-docs/skin all the *.css contain ^M.
> When using forrest -f publish.xml deploy, the same thing occurs with site-author/work/svn-deploy/forrest-docs/skin/*.css
> which I assume are taken from the build directory but still produce the error even if the build directory css files are cleaned up first.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira