RE: src/documentation/README
On Tue, 2002-12-10 at 19:17, Victor Mote wrote: OK, I see now that I misunderstood your Sorry, yes answer to Keiron. If http://forrestbot.cocoondev.org/site/xml-fop should be reflecting changes no more than an hour old made to xml-fop/src/documentation, then it is not working. I just looked for changes that were made about 24 hours ago, and they are not there. Also, as I mentioned, it shows a publish date of 12-7. So I suspect that something is not working. We have one document with a non-standard DTD (my fault, in fact that is what I am trying to work on) that might be messing up the flow. How do I go about troubleshooting this? Judging by the log it might be a DISPLAY problem. The compliance doc should only cause a broken link. Who is in charge of the cocoondev site, could they work out what the problem is? I think Sam Ruby has a script which automatically updates the live site to the contents of xml-site/targets/*. Should I contact him directly? Also, I still don't know whether xml-site/targets/fop is my final destination. What is best practices for this process? If this is documented somewhere, please excuse me -- I haven't found it yet. Also, I realize that this conversation might be better on forrest-dev. I asked on this list because I think Keiron has already figured most of this out I am trying to leverage off of that. Thanks very much for your help. Haven't figured out all of it. There is no real documentation for the old process, currently we are only really replacing the doc generation process. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Tue, Dec 10, 2002 at 11:17:25AM -0700, Victor Mote wrote:
...
See http://forrestbot.cocoondev.org/site/xml-fop
...
OK, I see now that I misunderstood your Sorry, yes answer to Keiron. If
http://forrestbot.cocoondev.org/site/xml-fop should be reflecting changes no
more than an hour old made to xml-fop/src/documentation, then it is not
working.
Hmm yes, something went wrong. It seems to be working now, but I'll keep
an eye on it. The 'last published' in the footer is the best indicator
of currency.
I think Sam Ruby has a script which automatically updates the live site
to the contents of xml-site/targets/*.
Should I contact him directly? Also, I still don't know whether
xml-site/targets/fop is my final destination. What is best practices for
this process? If this is documented somewhere, please excuse me -- I haven't
found it yet. Also, I realize that this conversation might be better on
forrest-dev. I asked on this list because I think Keiron has already figured
most of this out I am trying to leverage off of that. Thanks very much for
your help.
Forrest is in the same boat as FOP when it comes to site updates. AFAIK,
there are no docs, but the process is:
- Committers commit generated docs to xml-site/targets/{project}
- Every X hours, a script updates /www/xml.apache.org/ or wherever on
the live site, from CVS.
Pretty messy, but this CVS-based site update system has some virtues:
- it is pull-based, so fewer security risks
- site contents can be reverted easily without an admin having to figure
out how the doc generation tool works.
- it's there and it works
Discussions for creating a better site update system should probably be
held on general@xml, since it affects all projects, or forrest-dev, since
people there are particularly interested, and Steven has talked with Sam
about it before.
--Jeff
Victor Mote
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
RE: src/documentation/README
Jeff Turner wrote:
Forrest is in the same boat as FOP when it comes to site updates. AFAIK,
there are no docs, but the process is:
- Committers commit generated docs to xml-site/targets/{project}
- Every X hours, a script updates /www/xml.apache.org/ or wherever on
the live site, from CVS.
Pretty messy, but this CVS-based site update system has some virtues:
- it is pull-based, so fewer security risks
Pull wouldn't require CVS.
- site contents can be reverted easily without an admin having to figure
out how the doc generation tool works.
This makes sense.
- it's there and it works
Discussions for creating a better site update system should probably be
held on general@xml, since it affects all projects, or forrest-dev, since
people there are particularly interested, and Steven has talked with Sam
about it before.
I have no problem with xml-site/targets/{project} or the CVS-based system
(except for the binary PDF issue mentioned before, which may be
unavoidable). What is a little frustrating is that it seems like we are only
a short script (checkout, copy -r, commit) away from being able to use the
builds that are being done on icarus (or another apache machine) to update
xml-site/targets/{project}, instead of having to do the documentation builds
locally. Is there some reason why we can't just do a copy here?
Victor Mote
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Wed, Dec 11, 2002 at 03:15:33PM +0100, Nicola Ken Barozzi wrote: ... [On why http://forrestbot.cocoondev.org/sites/xml-fop/ wasn't updating] ... [java] Exception in thread main java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable. I added a DISPLAY pointing to Xvfb, and it seems to be updating properly now. If anyone notices a 'Last published' date at the bottom of a page older than 1 hour (GMT) please let me know. --Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Mon, Dec 09, 2002 at 09:45:06PM -0700, Victor Mote wrote: Keiron and Nicola Ken (and anyone else who is interested): I have the process of building the fop web site mostly scripted at /home/vmote/script/build-fop-website.bsh. I have a couple of problems/questions, which I will interject into the src/documentation/README doc contents below: The current procedure is: - checkout xml-forrest module - run: build.sh(bat) dist - follow instructions to set FORREST_HOME and path - go to xml-fop directory - run forrest(.bat) The documents will then be placed in build/site/ I have been running this on the Apache machine. Is that OK? If successful, we can theoretically just add a cron job to publish periodically if we wish, until Forrest is ready to do its magic for us. See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. --Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Tue, 2002-12-10 at 11:56, Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. You mean: and FOP that comes with Forrest. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Tue, Dec 10, 2002 at 05:26:48PM +0100, Keiron Liddle wrote: On Tue, 2002-12-10 at 11:56, Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. You mean: and FOP that comes with Forrest. Sorry, yes. Latest FOP XML source. --Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Tue, 2002-12-10 at 05:45, Victor Mote wrote: I have been running this on the Apache machine. Is that OK? If successful, we can theoretically just add a cron job to publish periodically if we wish, until Forrest is ready to do its magic for us. When running forrest, I am getting the NoClassDefFoundError on java.awt.Rectangle, which I assume is Batik failing during pdf generation because of running in a headless environment. I did not find any of our solutions in our headless FAQ available on that machine. How have you been handling this? Or have you been running locally then uploading the completed web site? I was running it locally. I wonder if we still should have this under cvs control. It probably doesn't matter much for the html files, but the pdf files are binary, and cvs is basically keeping a full copy of each revision. For example, status.pdf is currently 8328 bytes, and status.pdf,v which contains 3 versions, is 27,769 bytes. Since these are generated files now, we probably don't need an audit trail of them. I agree, I suppose it depends on the way it will function. Cvs just happens to be easy. Does committing the documents actually trigger something that immediately updates the web site, or is there some process that runs periodically that does that? I think there is something that does update it (for certain projects) at a certain time. I don't know if fop has it working. I am hoping, if this script works, that we can change our workflow as follows: If a reasonably good question comes up on the user list that can/should be addressed in our doc, the monitor (usually Joerg or Oleg) can change the doc, republish the web site, and post an answer that contains a link to the new doc, along with a comment that it was just updated. In this way, not only does the question get answered, but the doc is improved, for little more than the cost of answering it. This only works well if the doc can be republished almost at will. I'm hoping that the monitors would view this as an investment that should result in less questions on the user list (especially after our doc gets a reputation for being thorough), but, if not, I'll try to cull through the lists to update the doc myself. This would require a less-frequent update cycle -- once a day is probably plenty. My hope too. We could make the pdf's text (with the correct filter) but larger. One option might also be to disable the creation date which obviously changes each time. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: src/documentation/README
Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. I am really not yet following what is going on here. I understand the flow of files into xml-site/targets/fop. I assume that the link above is showing an hourly update of those contents (the xml-site/targets/fop is cvs, so it is getting checked out on a server somewhere). However, our published web site http://xml.apache.org/fop indicates that it was published on 12-2 (actually at the moment it says 12-3, so maybe it is now displaying GMT instead of PST), the forrestbot link above indicates that it was published on 12-7. So it would appear that for some reason those two are not the same. Am I missing something here? Most importantly, if I check files into xml-site/targets/fop, what steps, if any, do I need to take to get them visible at xml.apache.org/fop? Thanks for clarifying this. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
On Tue, Dec 10, 2002 at 10:24:28AM -0700, Victor Mote wrote: Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. I am really not yet following what is going on here. I understand the flow of files into xml-site/targets/fop. I assume that the link above is showing an hourly update of those contents (the xml-site/targets/fop is cvs, so it is getting checked out on a server somewhere). No, it is checking out xml-fop/src/documentation from CVS and building that with the latest Forrest. What you see there has no relation to what's in xml-site/targets/fop the same. Am I missing something here? Most importantly, if I check files into xml-site/targets/fop, what steps, if any, do I need to take to get them visible at xml.apache.org/fop? I think Sam Ruby has a script which automatically updates the live site to the contents of xml-site/targets/*. --Jeff Thanks for clarifying this. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: src/documentation/README
Jeff Turner wrote: On Tue, Dec 10, 2002 at 10:24:28AM -0700, Victor Mote wrote: Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. I am really not yet following what is going on here. I understand the flow of files into xml-site/targets/fop. I assume that the link above is showing an hourly update of those contents (the xml-site/targets/fop is cvs, so it is getting checked out on a server somewhere). No, it is checking out xml-fop/src/documentation from CVS and building that with the latest Forrest. What you see there has no relation to what's in xml-site/targets/fop OK, I see now that I misunderstood your Sorry, yes answer to Keiron. If http://forrestbot.cocoondev.org/site/xml-fop should be reflecting changes no more than an hour old made to xml-fop/src/documentation, then it is not working. I just looked for changes that were made about 24 hours ago, and they are not there. Also, as I mentioned, it shows a publish date of 12-7. So I suspect that something is not working. We have one document with a non-standard DTD (my fault, in fact that is what I am trying to work on) that might be messing up the flow. How do I go about troubleshooting this? I think Sam Ruby has a script which automatically updates the live site to the contents of xml-site/targets/*. Should I contact him directly? Also, I still don't know whether xml-site/targets/fop is my final destination. What is best practices for this process? If this is documented somewhere, please excuse me -- I haven't found it yet. Also, I realize that this conversation might be better on forrest-dev. I asked on this list because I think Keiron has already figured most of this out I am trying to leverage off of that. Thanks very much for your help. Victor Mote - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: src/documentation/README
Victor Mote wrote: Jeff Turner wrote: On Tue, Dec 10, 2002 at 10:24:28AM -0700, Victor Mote wrote: Jeff Turner wrote: See http://forrestbot.cocoondev.org/site/xml-fop Updated every hour with the latest Forrest and FOP source. I am really not yet following what is going on here. I understand the flow of files into xml-site/targets/fop. I assume that the link above is showing an hourly update of those contents (the xml-site/targets/fop is cvs, so it is getting checked out on a server somewhere). No, it is checking out xml-fop/src/documentation from CVS and building that with the latest Forrest. What you see there has no relation to what's in xml-site/targets/fop OK, I see now that I misunderstood your Sorry, yes answer to Keiron. If http://forrestbot.cocoondev.org/site/xml-fop should be reflecting changes no more than an hour old made to xml-fop/src/documentation, then it is not working. I just looked for changes that were made about 24 hours ago, and they are not there. Also, as I mentioned, it shows a publish date of 12-7. So I suspect that something is not working. We have one document with a non-standard DTD (my fault, in fact that is what I am trying to work on) that might be messing up the flow. How do I go about troubleshooting this? I think Sam Ruby has a script which automatically updates the live site to the contents of xml-site/targets/*. Should I contact him directly? Also, I still don't know whether xml-site/targets/fop is my final destination. What is best practices for this process? If this is documented somewhere, please excuse me -- I haven't found it yet. Also, I realize that this conversation might be better on forrest-dev. I asked on this list because I think Keiron has already figured most of this out I am trying to leverage off of that. Thanks very much for your help. Victor, Jeff, Please keep this conversation here. I, too, am finding this process very confusing, but all of the committers need to be aware of the way the FOP web-site updates work, and we can't do that if the conversation disappears. Peter -- Peter B. West [EMAIL PROTECTED] http://www.powerup.com.au/~pbwest/ Lord, to whom shall we go? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
