You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Tony Collen <co...@umn.edu> on 2005/09/08 20:03:59 UTC
patch commit request
Hey,
Would someone be so kind as to apply this patch to trunk and 2.1.x branch:
http://issues.apache.org/bugzilla/show_bug.cgi?id=36326
I'm unable to commit anything because my laptop is having some major
hardware issues, and it's out of commission until I get it straightened out.
Also, there are a couple submitted "livesites" that I was going to do,
but can't work on for the same reason... could someone slap those in, also?
Thanks,
----
Tony, who hasn't done much with Cocoon lately, and is also planning on
making a trip to the Apple store for another possible motherboard
replacement.
Re: patch commit request
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Jorg Heymans wrote:
> Alternatively we could clean out that page in the current xdocs and put
> a link to the migrated content in daisy.
-1: Daisy is (becoming) staging for our docs which will be published at the main
site. Please do not link to the staging area, link to the official site only.
Vadim
Re: howto update the website using forrest (was Re: patch commit request)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 10 sept. 05, à 01:06, Jorg Heymans a écrit :
> ...The updated livesites page is now on minotaur. It is not visible to
> the
> outside world yet, there's probably a cache in between waiting to
> expire...
Websites are replicated from there to the machine that serves the
public sites, every few hours.
That's the why changes don't appear immediately.
-Bertrand
Re: howto update the website using forrest (was Re: patch commit
request)
Posted by Jorg Heymans <jh...@domek.be>.
Jorg Heymans wrote:
> I have a broken forrest installation on my machine somehow and I have no
> idea how to fix it.
>
and one minute after sending this email I fixed it.
The updated livesites page is now on minotaur. It is not visible to the
outside world yet, there's probably a cache in between waiting to expire.
Jorg
Re: howto update the website using forrest (was Re: patch commit
request)
Posted by Jorg Heymans <jh...@domek.be>.
David Crossley wrote:
>>In the meantime i would be very grateful if someone could tell me what
>>needs to be done to update the website. I tried to run forrest locally
>>from the main cocoon-site directory but it failed :
>>
I have a broken forrest installation on my machine somehow and I have no
idea how to fix it.
If someone is able to regenerate the site (or at least
livesites-2.1.xml) feel free to do so.
Thanks
Jorg
Re: howto update the website using forrest (was Re: patch commit request)
Posted by David Crossley <cr...@apache.org>.
Jorg Heymans wrote:
> hepabolu wrote:
>
> > Ok, let's add to both for the time being. I have no idea how much there
> > is to add to Daisy, but in the process you might check if they are still
> > valid links.
>
> i've added all bugzilla [link] entries to livesites-2.1.xml - what a
> pain. I'll copy the content in bulk to Daisy in a bit.
>
> In the meantime i would be very grateful if someone could tell me what
> needs to be done to update the website. I tried to run forrest locally
> from the main cocoon-site directory but it failed :
>
> Lazy mode: true
> X [0] linkmap.html BROKEN: The
> element type "lenya" must be terminated by the matching end-tag "</lenya>".
> Logging Error: Writing event to closed stream.
> Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
> D:\tools\apache-forrest-0.7\main\targets\site.xml:41: Java returned: 1
>
> Any forresters around to help out ?
http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
See section C) ... need to use Forrest-v0.6
I just fixed a broken closing tag for <lenya> in
the site.xml navigation file.
-David
Re: howto update the website using forrest (was Re: patch commit
request)
Posted by Jorg Heymans <jh...@domek.be>.
Ross Gardler wrote:
> You'd be better off on the Forrest user list for this kind of help. I
> spotted this one, but may not spot them all, over there you are sure of
> our attention.
I've posted my progress to forrest-users. It is still not quite working
though.
Jorg
Re: howto update the website using forrest (was Re: patch commit
request)
Posted by Ross Gardler <rg...@apache.org>.
Jorg Heymans wrote:
> hepabolu wrote:
>
>
>>Ok, let's add to both for the time being. I have no idea how much there
>>is to add to Daisy, but in the process you might check if they are still
>> valid links.
>
>
> i've added all bugzilla [link] entries to livesites-2.1.xml - what a
> pain. I'll copy the content in bulk to Daisy in a bit.
>
> In the meantime i would be very grateful if someone could tell me what
> needs to be done to update the website. I tried to run forrest locally
> from the main cocoon-site directory but it failed :
>
> Lazy mode: true
> X [0] linkmap.html BROKEN: The
> element type "lenya" must be terminated by the matching end-tag "</lenya>".
This is an XML validation error. It should be highlighted before you get
to this stage as forest, by default, validates all documents before
attempting to build. This is configurable though and may be turned off
in your config.
Try "forrest validate" to give you more info. (although a clue for you
is that linkmap.html is gneerated from your site.xml file, chances are
that file is not well-formed.
> Logging Error: Writing event to closed stream.
That's a known issue and can be ignored.
> Any forresters around to help out ?
You'd be better off on the Forrest user list for this kind of help. I
spotted this one, but may not spot them all, over there you are sure of
our attention.
Ross
Re: howto update the website using forrest (was Re: patch commit
request)
Posted by hepabolu <he...@gmail.com>.
> Lazy mode: true
> X [0] linkmap.html BROKEN: The
> element type "lenya" must be terminated by the matching end-tag "</lenya>".
> Logging Error: Writing event to closed stream.
> Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
> D:\tools\apache-forrest-0.7\main\targets\site.xml:41: Java returned: 1
>
>
> Any forresters around to help out ?
Last time I asked about site updates I got this link:
http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
I hope it helps.
Bye, Helma
howto update the website using forrest (was Re: patch commit request)
Posted by Jorg Heymans <jh...@domek.be>.
hepabolu wrote:
>
> Ok, let's add to both for the time being. I have no idea how much there
> is to add to Daisy, but in the process you might check if they are still
> valid links.
i've added all bugzilla [link] entries to livesites-2.1.xml - what a
pain. I'll copy the content in bulk to Daisy in a bit.
In the meantime i would be very grateful if someone could tell me what
needs to be done to update the website. I tried to run forrest locally
from the main cocoon-site directory but it failed :
Lazy mode: true
X [0] linkmap.html BROKEN: The
element type "lenya" must be terminated by the matching end-tag "</lenya>".
Logging Error: Writing event to closed stream.
Total time: 0 minutes 9 seconds, Site size: 0 Site pages: 0
BUILD FAILED
D:\tools\apache-forrest-0.7\main\targets\site.xml:41: Java returned: 1
Any forresters around to help out ?
Thanks
Jorg
Re: patch commit request
Posted by Geoff Howard <ge...@gmail.com>.
Yes, that's what I figured - I'll experiment a little.
On 9/13/05, hepabolu <he...@gmail.com> wrote:
> Geoff Howard wrote:
> > Confirmed - thanks. Went and corrected a few typos just to get my
> > feet wet. Simple and quick - just what we have needed. Thanks to all
> > who worked to get this set up!
> >
> > Anyone have ideas on how to edit disconnected? (e.g., on the plane)
>
> I don't think that is currently possible. OTOH it's just plain HTML.
> What you could do is study the tags used (just switch to textareas view
> with the button on the top right above the edit box) and write your text
> using these tags in a simple text editor and copy and paste them in later.
>
> HTH.
>
> Bye, Helma
>
Re: patch commit request
Posted by hepabolu <he...@gmail.com>.
Geoff Howard wrote:
> Confirmed - thanks. Went and corrected a few typos just to get my
> feet wet. Simple and quick - just what we have needed. Thanks to all
> who worked to get this set up!
>
> Anyone have ideas on how to edit disconnected? (e.g., on the plane)
I don't think that is currently possible. OTOH it's just plain HTML.
What you could do is study the tags used (just switch to textareas view
with the button on the top right above the edit box) and write your text
using these tags in a simple text editor and copy and paste them in later.
HTH.
Bye, Helma
Re: patch commit request
Posted by Geoff Howard <ge...@gmail.com>.
Confirmed - thanks. Went and corrected a few typos just to get my
feet wet. Simple and quick - just what we have needed. Thanks to all
who worked to get this set up!
Anyone have ideas on how to edit disconnected? (e.g., on the plane)
Geoff
On 9/9/05, Upayavira <uv...@odoko.co.uk> wrote:
> Geoff Howard wrote:
> > ooops....
> >
> > so can you boost my rights too?
>
> done.
>
> Upayavira
>
Re: patch commit request
Posted by Upayavira <uv...@odoko.co.uk>.
Geoff Howard wrote:
> ooops....
>
> so can you boost my rights too?
done.
Upayavira
Re: patch commit request
Posted by Geoff Howard <ge...@gmail.com>.
ooops....
so can you boost my rights too?
On 9/9/05, Geoff Howard <ge...@gmail.com> wrote:
> FYI, I think I've created a daisy account and might start taking a
> whack at documentation.
>
> On 9/9/05, Upayavira <uv...@odoko.co.uk> wrote:
> > Jorg Heymans wrote:
> > > Upayavira wrote:
> > >
> > >>Let us know when you've created your account.
> > >>
> > >
> > >
> > > created.
> >
> > You now have doc-editor and doc-committer rights.
> >
> > Regards, Upayavira
> >
>
Re: patch commit request
Posted by Geoff Howard <ge...@gmail.com>.
FYI, I think I've created a daisy account and might start taking a
whack at documentation.
On 9/9/05, Upayavira <uv...@odoko.co.uk> wrote:
> Jorg Heymans wrote:
> > Upayavira wrote:
> >
> >>Let us know when you've created your account.
> >>
> >
> >
> > created.
>
> You now have doc-editor and doc-committer rights.
>
> Regards, Upayavira
>
Re: patch commit request
Posted by Upayavira <uv...@odoko.co.uk>.
Jorg Heymans wrote:
> Upayavira wrote:
>
>>Let us know when you've created your account.
>>
>
>
> created.
You now have doc-editor and doc-committer rights.
Regards, Upayavira
Re: patch commit request
Posted by Jorg Heymans <jh...@domek.be>.
Upayavira wrote:
>
> Let us know when you've created your account.
>
created.
Re: patch commit request
Posted by Upayavira <uv...@odoko.co.uk>.
Jorg Heymans wrote:
> hepabolu wrote:
>
>
>>Ok, let's add to both for the time being. I have no idea how much there
>>is to add to Daisy, but in the process you might check if they are still
>> valid links.
>
>
> I guess i will need a daisy account to add content right? Can someone
> create me one ? (username jheymans)
You create an account, then someone gives you committer rights (e.g. me)
Let us know when you've created your account.
Upayavira
Re: patch commit request
Posted by Jorg Heymans <jh...@domek.be>.
hepabolu wrote:
>
> Ok, let's add to both for the time being. I have no idea how much there
> is to add to Daisy, but in the process you might check if they are still
> valid links.
I guess i will need a daisy account to add content right? Can someone
create me one ? (username jheymans)
Thanks
Jorg
Re: patch commit request
Posted by hepabolu <he...@gmail.com>.
Jorg Heymans wrote:
>>We don't want to leave the submissions to the livesites too long
>>"invisible", but adding the info to the current xdocs rather than Daisy
>>looks like a waste of effort.
>
> agree.
>
> How about we add it to both for the time being? It's not like we're
> being flooded with these requests ATM so the duplication effort is limited.
>
> Alternatively we could clean out that page in the current xdocs and put
> a link to the migrated content in daisy.
Ok, let's add to both for the time being. I have no idea how much there
is to add to Daisy, but in the process you might check if they are still
valid links.
I plan to finish applying all bugfixes as mentioned in #34077 today (and
repeating the effort in TRUNK as well) and from then on I plan to
rebuild the current site navigation in Daisy. That should give us an
export of Daisy in the current site layout.
When Ross's plugin works, we could try a more frequent update of the
website.
Bye, Helma
Re: patch commit request
Posted by Jorg Heymans <jh...@domek.be>.
hepabolu wrote:
>> IIRC all it requires is a patch to the correct file in the docs. As
>> far as publishing the changes, IIRC (and I could be wrong on this),
>> you'd have to run Forrest on the docs, and then commit the new
>> generated page to the repo for the Cocoon website.
I tried looking for this file last night but only found
livesites-2.1.html , i take it there is an xml version of this
somewhere. Is this http://wiki.apache.org/cocoon/CocoonWebsiteUpdate
stuff still uptodate?
> We don't want to leave the submissions to the livesites too long
> "invisible", but adding the info to the current xdocs rather than Daisy
> looks like a waste of effort.
agree.
> I currently have no solution to this problem, someone else maybe?
How about we add it to both for the time being? It's not like we're
being flooded with these requests ATM so the duplication effort is limited.
Alternatively we could clean out that page in the current xdocs and put
a link to the migrated content in daisy.
WDYT?
Jorg
Re: patch commit request
Posted by hepabolu <os...@gmail.com>.
>>> Also, there are a couple submitted "livesites" that I was going to do,
>>> but can't work on for the same reason... could someone slap those in,
>>> also?
>>
>> I'll see if i can find out how to do this, again in few hours from now.
>
> IIRC all it requires is a patch to the correct file in the docs. As far
> as publishing the changes, IIRC (and I could be wrong on this), you'd
> have to run Forrest on the docs, and then commit the new generated page
> to the repo for the Cocoon website.
First of all: great that someone takes the time to go through the
process and add the livesites to the documentation site.
However, since we're trying to consolidate all documentation (and
livesites _IS_ part of the documentation) in Daisy at the cocoon.zone, I
think it is better to put the info there.
We don't want to leave the submissions to the livesites too long
"invisible", but adding the info to the current xdocs rather than Daisy
looks like a waste of effort.
I currently have no solution to this problem, someone else maybe?
Bye, Helma
Re: patch commit request
Posted by Jorg Heymans <jh...@domek.be>.
Tony Collen wrote:
>>> Would someone be so kind as to apply this patch to trunk and 2.1.x
>>> branch:
>>>
>>> http://issues.apache.org/bugzilla/show_bug.cgi?id=36326
done.
Jorg
Re: patch commit request
Posted by Tony Collen <co...@umn.edu>.
Jorg Heymans wrote:
>
> Tony Collen wrote:
>
>>Hey,
>>
>>Would someone be so kind as to apply this patch to trunk and 2.1.x branch:
>>
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=36326
>
>
> I'll do this in a few hours unless someone beats me to it.
Awesome, thanks!!!
>
>
>>Also, there are a couple submitted "livesites" that I was going to do,
>>but can't work on for the same reason... could someone slap those in, also?
>>
>
>
> I'll see if i can find out how to do this, again in few hours from now.
IIRC all it requires is a patch to the correct file in the docs. As far
as publishing the changes, IIRC (and I could be wrong on this), you'd
have to run Forrest on the docs, and then commit the new generated page
to the repo for the Cocoon website.
Tony
Re: patch commit request
Posted by Jorg Heymans <jh...@domek.be>.
Tony Collen wrote:
> Hey,
>
> Would someone be so kind as to apply this patch to trunk and 2.1.x branch:
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=36326
I'll do this in a few hours unless someone beats me to it.
> Also, there are a couple submitted "livesites" that I was going to do,
> but can't work on for the same reason... could someone slap those in, also?
>
I'll see if i can find out how to do this, again in few hours from now.
Regards
Jorg