Re: whitespace changes (Was: svn commit: r167890)
David Crossley wrote: DC It seemed to also do other reformatting. Be sure to do 'svn diff' DC before committing. Should I revert it back to the original whitespaceing and insert my changes again? -- Ferdinand Soethe
Re: whitespace changes (Was: svn commit: r167890)
Ferdinand Soethe wrote: David Crossley wrote: DC It seemed to also do other reformatting. Be sure to do 'svn diff' DC before committing. Should I revert it back to the original whitespaceing and insert my changes again? No. I was just making sure that people knew the problems that it causes. --David
Re: [RT] Serving Apache Forrest site from live Forrest
Nicola Ken Barozzi wrote: One thing I like about Forrest is that it's not only a static site generation engine, but it's capable of serving the site live. Changes are instantaneous, bandwith is perserved, and dynamic content can be employed. IMHO every Apache project that produces something it can use for itself *should* actually use it, like HTTPD does. This gives the team something to work collectively on, and a base that keeps the project adherent to actual needs. IOW, I would like to see the Forrest website served of a live Forrest instance. To do this, even before talking about logistics and permissions, we have to be sure that it's not going to cause problems, even in high load, and be able to administer it. Before we can seriously start to consider using it live, we should at least have the following: 1 - knowledge of the memory it's going to need and use 2 - have no known memory leakage (to be tested) 3 - have caching turned on 4 - know what to do when upgrading the version 5 - decide where it's going to get the site from 6 - other? After that, it would be beneficial to be able to serve multiple sites on a single Forrest instance, so that we can have other projects join and have their site served. Thoughts, comments, opinions? This is a RT thread so let us all throw our Random Thoughts into the mix. We can later develop that into a plan. I see various different issues. Some are separate, and some are entwined ... building our website (static, dynamic, both); a place to experiment with our own software; a testing environment; a way to stage the website so that we can review our changes before publishing; running a Forrestbot to build static websites for various ASF projects; etc. We will have a place to experiment soon. Each PMC will get $pmc.zones.apache.org ... they are still testing the setup, so there is no rush. That would be our space to experiment with our various versions of Forrest. We could have the release version, the head of trunk, and a known good trunk. I am not talking about versions of the docs, this is about versions of the software. We will need to experiment there, until we are happy to use it in production. We don't don't need to worry too much about memory usage at this stage. In fact, that zone will give us a place to do proper tests to determine the memory aspects. For our actual website, there are many things that we need to consider. For example, ASF Infrastructure has certain requirements to enable easy recovery of websites and a way to fail-over to another server to enable OS upgrades etc. I think that the main thing is to do it in steps. Start with the demo servers in forrest.zones.apache.org and work up to doing more ambitious things like the website. There is another related issue. Over the past years, a plan has come together to have a staging server, i.e. a place where static sites are built and previewed before going into production. That is now a lot closer to happening. See the threads at [EMAIL PROTECTED] about Site Build Zone, and also http://forrest.apache.org/0.7/proposal-asf-publish.html Of course, the Forrestbot is a part of that infrastructure and they want Forrest committers to be involved in that. Anyway, the zone is not ready yet, so i will keep us informed. --David
Re: Forrest sites google ranking
David Crossley wrote: Ross Gardler wrote: I just noticed that the changes in the Forrest site have resulted in a complete loss of our google ranking. That is we currently have a rank of n/a. Prior to the redirects we had a very healthy 7. Would you please explain how you find this ranking. https://addons.update.mozilla.org/extensions/moreinfo.php?application=firefoxid=262 Ross
Re: SVN Inconsitent Line Endings
David Crossley wrote: Ross Gardler wrote: Dave Brondsema wrote: I'd say we should find out why the HTML is generated with inconsistent line endings in the first place. True. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce cd into any plugin directory, do ant docs and check out the generated docs in build/site. Does the same behaviour happen if you use Forrest's packaged Ant? i.e. $FORREST_HOME/tools/ant/bin/ant docs Also 'unset ANT_HOME' to make it uses Forrest's lib/*.jar Yes I presume that this does not happen when you do 'forrest' to build the plugin's docs, rather than doing 'ant docs'. I had also assumed that, however it turns our to be incorrect. In fact doing forrest site on any site, including site-author, results in the same error. I can only assume that it has not raised it's head before because I have not been the first person to commit generated sites to SVN with the eol settings set to native. Given the above observation that the XSL generated comments ahve different line endings to other XSL generated files I can only assume it is something to do with the XSLT parser. For now I have put a workaround in place in the buildfile (uses an ant task to fix the line endings). I'll also place an issue on the issue tracker to remind us of this. Ross
[JIRA] Created: (FOR-492) Inconsitent Line Endings in generated sites
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-492 Here is an overview of the issue: - Key: FOR-492 Summary: Inconsitent Line Endings in generated sites Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 6 May 2005 10:04 AM Updated: Fri, 6 May 2005 10:04 AM Environment: Windows (with or without CYGWIN) Description: Sites generated by Forrest have inconsitent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce cd into any plugin directory, do ant docs and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? - 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//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-492) Inconsistent Line Endings in generated sites
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 6 May 2005 10:07 AM Changes: summary changed from Inconsitent Line Endings in generated sites to Inconsistent Line Endings in generated sites description changed from Sites generated by Forrest have inconsitent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce cd into any plugin directory, do ant docs and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? to Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? Fix Version changed to 0.8 - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-492?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-492 Here is an overview of the issue: - Key: FOR-492 Summary: Inconsistent Line Endings in generated sites Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 6 May 2005 10:04 AM Updated: Fri, 6 May 2005 10:07 AM Environment: Windows (with or without CYGWIN) Description: Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? - 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//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
