Re: Release and updating the website
Antonio Gallardo wrote: Hi David: The apidocs for cocoon 2.1.6 are now online: http://cocoon.apache.org/2.1/apidocs/ Thanks for your help. :-D Well thanks to you for taking up the challenge :-) --David
Re: Release and updating the website
Hi David: The apidocs for cocoon 2.1.6 are now online: http://cocoon.apache.org/2.1/apidocs/ Thanks for your help. :-D Best Regards, Antonio Gallardo. On Jue, 2 de Diciembre de 2004, 0:06, David Crossley dijo: > Antonio Gallardo wrote: >> On Mie, 1 de Diciembre de 2004, 23:07, Antonio Gallardo dijo: >> >>>On Mie, 1 de Diciembre de 2004, 17:21, David Crossley dijo: >>> Would someone else please update the "apidocs" on the website. The memory consumption by 'build javadocs' kills my build (using the default setting). >>> >>>If you wish, add more memory for javadocs: >>> >>>in file: tools/src/blocks-build.xsl at line 267. >> >> >> I wanted to help, but the instructions are confusing to me: >> >> http://cocoon.apache.org/2.1/apidocs/README.txt >> >> vs.: >> >> http://wiki.apache.org/cocoon/CocoonWebsiteUpdate >> >> The last document say to do an svn up and the first said don't copy >> javadocs there. Can someone explain how to do that? Please help. > > Both are correct. I just added a note to the latter: > > The javadocs are not stored in the cocoon-site SVN. > They can easily be regenerated. Use scp to copy them > to the website. > > --David > >
Re: Release and updating the website
On Jue, 2 de Diciembre de 2004, 0:06, David Crossley dijo: > Antonio Gallardo wrote: >> On Mie, 1 de Diciembre de 2004, 23:07, Antonio Gallardo dijo: >> >>>On Mie, 1 de Diciembre de 2004, 17:21, David Crossley dijo: >>> Would someone else please update the "apidocs" on the website. The memory consumption by 'build javadocs' kills my build (using the default setting). >>> >>>If you wish, add more memory for javadocs: >>> >>>in file: tools/src/blocks-build.xsl at line 267. >> >> >> I wanted to help, but the instructions are confusing to me: >> >> http://cocoon.apache.org/2.1/apidocs/README.txt >> >> vs.: >> >> http://wiki.apache.org/cocoon/CocoonWebsiteUpdate >> >> The last document say to do an svn up and the first said don't copy >> javadocs there. Can someone explain how to do that? Please help. > > Both are correct. I just added a note to the latter: > > The javadocs are not stored in the cocoon-site SVN. > They can easily be regenerated. Use scp to copy them > to the website. Thanks for the reply. Now I guess I can do that! ;-) I will update the javadocs. Best Regards, Antonio Gallardo.
Re: Release and updating the website
Antonio Gallardo wrote: On Mie, 1 de Diciembre de 2004, 23:07, Antonio Gallardo dijo: On Mie, 1 de Diciembre de 2004, 17:21, David Crossley dijo: Would someone else please update the "apidocs" on the website. The memory consumption by 'build javadocs' kills my build (using the default setting). If you wish, add more memory for javadocs: in file: tools/src/blocks-build.xsl at line 267. I wanted to help, but the instructions are confusing to me: http://cocoon.apache.org/2.1/apidocs/README.txt vs.: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate The last document say to do an svn up and the first said don't copy javadocs there. Can someone explain how to do that? Please help. Both are correct. I just added a note to the latter: The javadocs are not stored in the cocoon-site SVN. They can easily be regenerated. Use scp to copy them to the website. --David
Re: Release and updating the website
On Mie, 1 de Diciembre de 2004, 23:07, Antonio Gallardo dijo: > On Mie, 1 de Diciembre de 2004, 17:21, David Crossley dijo: >> Would someone else please update the "apidocs" >> on the website. The memory consumption by >> 'build javadocs' kills my build (using the >> default setting). > > If you wish, add more memory for javadocs: > > in file: tools/src/blocks-build.xsl at line 267. I wanted to help, but the instructions are confusing to me: http://cocoon.apache.org/2.1/apidocs/README.txt vs.: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate The last document say to do an svn up and the first said don't copy javadocs there. Can someone explain how to do that? Please help. Best Regards, Antonio Gallardo
Re: Release and updating the website
On Mie, 1 de Diciembre de 2004, 17:21, David Crossley dijo: > Would someone else please update the "apidocs" > on the website. The memory consumption by > 'build javadocs' kills my build (using the > default setting). If you wish, add more memory for javadocs: in file: tools/src/blocks-build.xsl at line 267. Best Regards, Antonio Gallardo.
Re: Release and updating the website
Would someone else please update the "apidocs" on the website. The memory consumption by 'build javadocs' kills my build (using the default setting). --David
Re: Release and updating the website
David Crossley wrote: I updated the Cocoon website today and then tried to clean up the instructions on the Wiki page CocoonWebsiteUpdate. Would another committer please try to follow thos instructions Wierd. Never mind. My browser must have cached the page. I did a reload and all is well. Ralph
Re: Release and updating the website
David Crossley wrote: I updated the Cocoon website today and then tried to clean up the instructions on the Wiki page CocoonWebsiteUpdate. Would another committer please try to follow thos instructions --David I'm curious. I see that the news page changed. Why didn't http://cocoon.apache.org/2.1/changes.html? I would hope that it would contain the latest status.xml whenever it is published. Ralph
Re: Release and updating the website
I updated the Cocoon website today and then tried to clean up the instructions on the Wiki page CocoonWebsiteUpdate. Would another committer please try to follow thos instructions --David
Re: Release and updating the website
Upayavira wrote: Bertrand Delacretaz wrote: find /final-site-dir -type f | sort > /tmp/f1 find /generated-stuff -type f | sort > /tmp/f2 diff /tmp/f1 /tmp/f2 >> Of course there are other ways, but I think this is practical. rsync -av --delete foo/ foo.old/ use the -n if you want to test first Great. That's useful. I'll add it to my list of things to check out, and document. Surely this'd be something for Forrest to automate? maybe because there is tools like rsync that provides this I did not see the urgent of doing this within forrest. Cheers, Cheche
Re: Release and updating the website
Bertrand Delacretaz wrote: Le 23 nov. 04, à 06:42, David Crossley a écrit : David Crossley wrote: Upayavira wrote: Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN... I'm with David here (i.e. generating in build/site as now) - if you generate directly into the final tree I think it's much harder to find out which files must be *deleted* from the final destination. Generating somewhere else allows you to compare lists of files to find out what must be removed, e.g. find /final-site-dir -type f | sort > /tmp/f1 find /generated-stuff -type f | sort > /tmp/f2 diff /tmp/f1 /tmp/f2 Of course there are other ways, but I think this is practical. Great. That's useful. I'll add it to my list of things to check out, and document. Surely this'd be something for Forrest to automate? Could the CLI keep a list of pages it generates, and then compare the newly generated list with this? It would then know what to delete, if a switch has been added. Just a thought. Regards, Upayavira
Re: Release and updating the website
Le 23 nov. 04, à 06:42, David Crossley a écrit : David Crossley wrote: Upayavira wrote: Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN... I'm with David here (i.e. generating in build/site as now) - if you generate directly into the final tree I think it's much harder to find out which files must be *deleted* from the final destination. Generating somewhere else allows you to compare lists of files to find out what must be removed, e.g. find /final-site-dir -type f | sort > /tmp/f1 find /generated-stuff -type f | sort > /tmp/f2 diff /tmp/f1 /tmp/f2 Of course there are other ways, but I think this is practical. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Release and updating the website
David Crossley wrote: Upayavira wrote: Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN. We can change the location of where the documents get generated via forrest.properties config. Actually i prefer them to go to build/site/ as now. I can do 'diff -rq' to see what has changed, and importantly what files were added/deleted. But i suppose that files are not deleted often, so the diff and "adds" could be found with svn commands. Another reason is if you only want to update one or two documents, then it is easy to copy them over from build/site/ directory. I suppose that one could do 'svn commit" for the specific docs, then 'svn revert' the rest. I will go with whatever people want. More importantly whatever makes it clear and easy for those who are not experienced with the documentation production. --David
Re: Release and updating the website
On Mon, 22 Nov 2004, David Crossley wrote: > Upayavira wrote: > > I see you've fixed some of these on the wiki. Thanks. Also, the page > > refers to a default.properties file. I can't find such a file, nor can I > > find any reference to it in Cocoon's build target files. Am I supposed > > to use a property to set it, or environment variable, or a > > local.build.properties? > > Hmmm, i don't know. The best way is to set > FORREST_HOME and PATH as described when you install > Forrest. Then the Cocoon build script will use that. > > --David hi i have post my experiences in wiki http://wiki.apache.org/cocoon/CocoonWebsiteUpdate i have try to follow those instruction (unsuccesfull) --stavros > > >
Re: Release and updating the website
Upayavira wrote: I see you've fixed some of these on the wiki. Thanks. Also, the page refers to a default.properties file. I can't find such a file, nor can I find any reference to it in Cocoon's build target files. Am I supposed to use a property to set it, or environment variable, or a local.build.properties? Hmmm, i don't know. The best way is to set FORREST_HOME and PATH as described when you install Forrest. Then the Cocoon build script will use that. --David
Re: Release and updating the website
Upayavira wrote: David Crossley wrote: I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. Would you please explain that obscure comment. Let us all help to fix the instructions then. Sorry, wasn't trying to be cryptic - I was referring to the wiki instructions. Sure. (Sorry i accidently snipped the Wiki URL.) I meant that we need to work together to fix the description. It is strange that no-one has raised issues about this document in the past. I suppose that those of us who have been updating the site already know what to do. I have already started to update it, but want to understand things a bit more before I do so. But, in the name of openness, here's some of the stuff I've struggled with on this wiki page so far: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate In part, I think it could do with more explanation as to why to do things certain ways, e.g. 0.5 will give you strange artefacts on your pages, whilst Cocoon's docs will need to be upgraded to work with 0.6. In fact, it suggests using a "stable" forrest, such as 0.5. That could imply that 0.6 is okay, which it isn't. Yes. I added something earlier today to help with that. Also, it says run "build site". Not sure if there actually is a "site" target though. I think that it might be "build docs". Then, it makes no reference to the cocoon-site module, which actually doesn't have a build process of its own, so you'll need to use Forrest directly there, I suspect. That is correct. Just do 'forrest' in the top-level of the cocoon-site module. Be sure to set the FORREST_HOME and PATH environemnt variables. My guess is that this wiki page has not been updated since we split the top-level docs out from the version-specific docs, i.e. a long time ago. Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN. We can change the location of where the documents get generated via forrest.properties config. Then, the page says "copy jimi-1.0.jar into lib/core in Forrest. But Forrest only has lib/endorsed and lib/optional. Typo i think. I have it in lib/optional Those are some of the problems I had with the wiki page. I'll keep plugging on until I've got it working here, and will make sure any lessons appear here and on the wiki. Great. I will try to help. --David
Re: Release and updating the website
Upayavira wrote: David Crossley wrote: I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. Would you please explain that obscure comment. Let us all help to fix the instructions then. Sorry, wasn't trying to be cryptic - I was referring to the wiki instructions. I have already started to update it, but want to understand things a bit more before I do so. But, in the name of openness, here's some of the stuff I've struggled with on this wiki page so far: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate In part, I think it could do with more explanation as to why to do things certain ways, e.g. 0.5 will give you strange artefacts on your pages, whilst Cocoon's docs will need to be upgraded to work with 0.6. In fact, it suggests using a "stable" forrest, such as 0.5. That could imply that 0.6 is okay, which it isn't. Also, it says run "build site". Not sure if there actually is a "site" target though. Then, it makes no reference to the cocoon-site module, which actually doesn't have a build process of its own, so you'll need to use Forrest directly there, I suspect. Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN. Then, the page says "copy jimi-1.0.jar into lib/core in Forrest. But Forrest only has lib/endorsed and lib/optional. Those are some of the problems I had with the wiki page. I'll keep plugging on until I've got it working here, and will make sure any lessons appear here and on the wiki. Regards, Upayavira I see you've fixed some of these on the wiki. Thanks. Also, the page refers to a default.properties file. I can't find such a file, nor can I find any reference to it in Cocoon's build target files. Am I supposed to use a property to set it, or environment variable, or a local.build.properties? Regards, Upayavira
Re: Release and updating the website
David Crossley wrote: I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. Would you please explain that obscure comment. Let us all help to fix the instructions then. Sorry, wasn't trying to be cryptic - I was referring to the wiki instructions. I have already started to update it, but want to understand things a bit more before I do so. But, in the name of openness, here's some of the stuff I've struggled with on this wiki page so far: http://wiki.apache.org/cocoon/CocoonWebsiteUpdate In part, I think it could do with more explanation as to why to do things certain ways, e.g. 0.5 will give you strange artefacts on your pages, whilst Cocoon's docs will need to be upgraded to work with 0.6. In fact, it suggests using a "stable" forrest, such as 0.5. That could imply that 0.6 is okay, which it isn't. Also, it says run "build site". Not sure if there actually is a "site" target though. Then, it makes no reference to the cocoon-site module, which actually doesn't have a build process of its own, so you'll need to use Forrest directly there, I suspect. Also, when I did run Forrest, I really had to dig to find the generated pages, whereas I would have expected them to have been generated "in place", i.e. into the place from which I'd commit them directly to SVN. Then, the page says "copy jimi-1.0.jar into lib/core in Forrest. But Forrest only has lib/endorsed and lib/optional. Those are some of the problems I had with the wiki page. I'll keep plugging on until I've got it working here, and will make sure any lessons appear here and on the wiki. Regards, Upayavira
Re: Release and updating the website
On Mon, 22 Nov 2004, David Crossley wrote: > Upayavira wrote: > > Bertrand Delacretaz wrote: > > > >> Le 19 nov. 04, Γ 17:23, [EMAIL PROTECTED] a Γ©crit : > >> > >>> On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: > >>> > Le 19 nov. 04, Ξ° 16:05, Upayavira a ΞΉcrit : > > > ...Thus, the site needs to be regenerated with Forrest, which, to > > date, I haven't done. > > > > You probably know this already: there are instructions at > http://wiki.apache.org/cocoon/CocoonWebsiteUpdate > >>> > >>> > >>> > >>> the site is not moved to SVN? > >>> here the instructions are talking about CVS? > >> > >> > >> > >> You're right, it's svn instead of cvs now. We need to update that page. > > > > > > I'll do that too, if I can get Forrest to work. Unfortunately the above > > link doesn't entirely make sense. > > Would you please explain that obscure comment. > Let us all help to fix the instructions then. > > --David > hi david there is problem with ant when you try build site in cocoon 2.1.6 you will get some errors i'll post the details. --stavros
Re: Release and updating the website
Upayavira wrote: Bertrand Delacretaz wrote: Le 19 nov. 04, Ã 17:23, [EMAIL PROTECTED] a Ãcrit : On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: Le 19 nov. 04, Î 16:05, Upayavira a Îcrit : ...Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. You probably know this already: there are instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate the site is not moved to SVN? here the instructions are talking about CVS? You're right, it's svn instead of cvs now. We need to update that page. I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. Would you please explain that obscure comment. Let us all help to fix the instructions then. --David
generating the docs with Forrest (was: Release and updating the website)
Le 19 nov. 04, à 19:49, Upayavira a écrit : http://wiki.apache.org/cocoon/CocoonWebsiteUpdate ... I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. FYI I have tried the following, no success at this point. But I haven't done this in a looong time. 1) get forrest 0.6 binary, configure as indicated in readme 2) cd BRANCH_2_1_X, build clean 3) run forrest from same directory I get this message Cannot find CatalogManager.properties And a few seconds later this error which stops forrest. X [0] linkmap.html BROKEN: /home/bert/workspace/apache/cocoon-2.2/BRANCH_2_1_X/src/documentation/ skins/pelt/xslt/html/site2xhtml.xsl (No such file or directory) Also tried with forrest 0.5.1, no success either (tried "forrest" not "build site"). Note that our forrest-related configs apparently need to be updated for forrest 0.6, dunno if it's been done yet (http://forrest.apache.org/docs/upgrading_06.html). Gotta run to other stuff now, won't have more time for this today. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Release and updating the website
On Fri, 19 Nov 2004, Upayavira wrote: > Bertrand Delacretaz wrote: > > > Le 19 nov. 04, Γ 17:23, [EMAIL PROTECTED] a Γ©crit : > > > >> On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: > >> > >>> Le 19 nov. 04, Ξ° 16:05, Upayavira a ΞΉcrit : > >>> > ...Thus, the site needs to be regenerated with Forrest, which, to > date, I haven't done. > >>> > >>> > >>> You probably know this already: there are instructions at > >>> http://wiki.apache.org/cocoon/CocoonWebsiteUpdate > >> > >> > >> the site is not moved to SVN? > >> here the instructions are talking about CVS? > > > > > > You're right, it's svn instead of cvs now. We need to update that page. > > I'll do that too, if I can get Forrest to work. Unfortunately the above > link doesn't entirely make sense. i'm trying to build site all this time too but i think that they are many issues that make this impossible .. i'll keep trying, and i'll reply here with a summary. --stavros > > Regards, Upayavira > >
Re: Release and updating the website
Bertrand Delacretaz wrote: Le 19 nov. 04, Ã 17:23, [EMAIL PROTECTED] a Ãcrit : On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: Le 19 nov. 04, Î 16:05, Upayavira a Îcrit : ...Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. You probably know this already: there are instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate the site is not moved to SVN? here the instructions are talking about CVS? You're right, it's svn instead of cvs now. We need to update that page. I'll do that too, if I can get Forrest to work. Unfortunately the above link doesn't entirely make sense. Regards, Upayavira
Re: Release and updating the website
Le 19 nov. 04, Ã 17:23, [EMAIL PROTECTED] a Ãcrit : On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: Le 19 nov. 04, Î 16:05, Upayavira a Îcrit : ...Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. You probably know this already: there are instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate the site is not moved to SVN? here the instructions are talking about CVS? You're right, it's svn instead of cvs now. We need to update that page. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Release and updating the website
Bertrand Delacretaz wrote: Le 19 nov. 04, à 16:05, Upayavira a écrit : ...Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. You probably know this already: there are instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate :-) That's what I'll be following. I should have said. Regards, Upayavira
Re: Release and updating the website
On Fri, 19 Nov 2004, Upayavira wrote: > [EMAIL PROTECTED] wrote: > > >the pages that must be updated are : > >- http://cocoon.apache.org/news/ > >- http://cocoon.apache.org/2.1/index.html > > > >i can prepare a path tonight, if nobody else has done something until now > > > >but .. if i remember correctly the gif/link to apacheCon is hard coded in > >produced html page and not in sources? > > > > > Which doesn't matter as ApacheCon is over now. > > Do create a patch, and I'll try to work out how to produce the site. > > Upayavira > 2.1/index.html's sources are in cocoon's release_2_1_6 repository and are created after build i have it in my local directory now but i dont know if i have to put it somewhere? --stavros > >On Fri, 19 Nov 2004, Carsten Ziegeler wrote: > > > > > > > >>Hi, > >> > >>can anyone please update the website? The release is out; I just send > >>the announcement mail. > >> > >>I'm not able to update the site in the next four weeks, as I will go > >>on vacation (hurray) without a computer or internet connection. So I > >>will remain silent within the next weeks :) > >> > >>See you > >> > >>Carsten > >> > >>Carsten Ziegeler > >>Open Source Group, S&N AG > >>http://www.s-und-n.de > >>http://www.osoco.net/weblogs/rael/ > >> > >> > >> > >> > > > > > > > > > >
Re: Release and updating the website
On Fri, 19 Nov 2004, Bertrand Delacretaz wrote: > Le 19 nov. 04, ΰ 16:05, Upayavira a ιcrit : > > ...Thus, the site needs to be regenerated with Forrest, which, to > > date, I haven't done. > > You probably know this already: there are instructions at > http://wiki.apache.org/cocoon/CocoonWebsiteUpdate the site is not moved to SVN? here the instructions are talking about CVS? --stavros > > I might try it tomorrow if you don't beat me to it, not sure if I'll > find time though. I'll indicate here if I get to doing it. > -Bertrand >
Re: Release and updating the website
[EMAIL PROTECTED] wrote: the pages that must be updated are : - http://cocoon.apache.org/news/ - http://cocoon.apache.org/2.1/index.html i can prepare a path tonight, if nobody else has done something until now but .. if i remember correctly the gif/link to apacheCon is hard coded in produced html page and not in sources? Which doesn't matter as ApacheCon is over now. Do create a patch, and I'll try to work out how to produce the site. Upayavira On Fri, 19 Nov 2004, Carsten Ziegeler wrote: Hi, can anyone please update the website? The release is out; I just send the announcement mail. I'm not able to update the site in the next four weeks, as I will go on vacation (hurray) without a computer or internet connection. So I will remain silent within the next weeks :) See you Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.net/weblogs/rael/
Re: Release and updating the website
Le 19 nov. 04, à 16:05, Upayavira a écrit : ...Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. You probably know this already: there are instructions at http://wiki.apache.org/cocoon/CocoonWebsiteUpdate I might try it tomorrow if you don't beat me to it, not sure if I'll find time though. I'll indicate here if I get to doing it. -Bertrand smime.p7s Description: S/MIME cryptographic signature
Re: Release and updating the website
[EMAIL PROTECTED] wrote: On Fri, 19 Nov 2004, Upayavira wrote: Ralph Goers wrote: [EMAIL PROTECTED] wrote: the pages that must be updated are : - http://cocoon.apache.org/news/ - http://cocoon.apache.org/2.1/index.html i can prepare a path tonight, if nobody else has done something until now but .. if i remember correctly the gif/link to apacheCon is hard coded in produced html page and not in sources? How does http://cocoon.apache.org/2.1/changes.html get updated? I suspect that this is generated by Forrest from the status.xml file. Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. I may have a play to see if I can get this going, as I'd like to be in a position to update the site itself, but as yet cannot make any promises. if you decide to play with that consider the patch for the news page in bugzilla Yes, I spotted that. Regards, Upayavira
Re: Release and updating the website
On Fri, 19 Nov 2004, Carsten Ziegeler wrote: Hi, can anyone please update the website? The release is out; I just send the announcement mail. I'm not able to update the site in the next four weeks, as I will go on vacation (hurray) without a computer or internet connection. So I will remain silent within the next weeks :) Nice holidays, than :-) -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com
Re: Release and updating the website
On Fri, 19 Nov 2004, Upayavira wrote: > Ralph Goers wrote: > > > [EMAIL PROTECTED] wrote: > > > >> the pages that must be updated are : > >> - http://cocoon.apache.org/news/ > >> - http://cocoon.apache.org/2.1/index.html > >> > >> i can prepare a path tonight, if nobody else has done something until > >> now > >> > >> but .. if i remember correctly the gif/link to apacheCon is hard > >> coded in produced html page and not in sources? > >> > >> > > How does http://cocoon.apache.org/2.1/changes.html get updated? > > I suspect that this is generated by Forrest from the status.xml file. > > Thus, the site needs to be regenerated with Forrest, which, to date, I > haven't done. > > I may have a play to see if I can get this going, as I'd like to be in a > position to update the site itself, but as yet cannot make any promises. if you decide to play with that consider the patch for the news page in bugzilla --stavros > > Regards, Upayavira > >
Re: Release and updating the website
Ralph Goers wrote: [EMAIL PROTECTED] wrote: the pages that must be updated are : - http://cocoon.apache.org/news/ - http://cocoon.apache.org/2.1/index.html i can prepare a path tonight, if nobody else has done something until now but .. if i remember correctly the gif/link to apacheCon is hard coded in produced html page and not in sources? How does http://cocoon.apache.org/2.1/changes.html get updated? I suspect that this is generated by Forrest from the status.xml file. Thus, the site needs to be regenerated with Forrest, which, to date, I haven't done. I may have a play to see if I can get this going, as I'd like to be in a position to update the site itself, but as yet cannot make any promises. Regards, Upayavira
Re: Release and updating the website
[EMAIL PROTECTED] said: > On Fri, 19 Nov 2004, Ralph Goers wrote: >> How does http://cocoon.apache.org/2.1/changes.html get updated? >> >> > > i can't find the sources for this > i have look at: > http://svn.apache.org/repos/asf/cocoon/tags/RELEASE_2_1_6/src/documentation/xdocs/ > http://svn.apache.org/repos/asf/cocoon/site/src/documentation/content/xdocs/ I believe it derives from status.xml. You can view it when you build 2.1.6 in the sample site. I just wonder how it makes it to the web site.
Re: Release and updating the website
On Fri, 19 Nov 2004, Ralph Goers wrote: > [EMAIL PROTECTED] wrote: > > >the pages that must be updated are : > >- http://cocoon.apache.org/news/ > >- http://cocoon.apache.org/2.1/index.html > > > >i can prepare a path tonight, if nobody else has done something until now > > > >but .. if i remember correctly the gif/link to apacheCon is hard coded in > >produced html page and not in sources? > > > > > How does http://cocoon.apache.org/2.1/changes.html get updated? > > i can't find the sources for this i have look at: http://svn.apache.org/repos/asf/cocoon/tags/RELEASE_2_1_6/src/documentation/xdocs/ http://svn.apache.org/repos/asf/cocoon/site/src/documentation/content/xdocs/
Re: Release and updating the website
[EMAIL PROTECTED] wrote: the pages that must be updated are : - http://cocoon.apache.org/news/ - http://cocoon.apache.org/2.1/index.html i can prepare a path tonight, if nobody else has done something until now but .. if i remember correctly the gif/link to apacheCon is hard coded in produced html page and not in sources? How does http://cocoon.apache.org/2.1/changes.html get updated?
Re: Release and updating the website
the pages that must be updated are : - http://cocoon.apache.org/news/ - http://cocoon.apache.org/2.1/index.html i can prepare a path tonight, if nobody else has done something until now but .. if i remember correctly the gif/link to apacheCon is hard coded in produced html page and not in sources? -- stavros On Fri, 19 Nov 2004, Carsten Ziegeler wrote: > Hi, > > can anyone please update the website? The release is out; I just send > the announcement mail. > > I'm not able to update the site in the next four weeks, as I will go > on vacation (hurray) without a computer or internet connection. So I > will remain silent within the next weeks :) > > See you > > Carsten > > Carsten Ziegeler > Open Source Group, S&N AG > http://www.s-und-n.de > http://www.osoco.net/weblogs/rael/ > >
Release and updating the website
Hi, can anyone please update the website? The release is out; I just send the announcement mail. I'm not able to update the site in the next four weeks, as I will go on vacation (hurray) without a computer or internet connection. So I will remain silent within the next weeks :) See you Carsten Carsten Ziegeler Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.net/weblogs/rael/
