You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Clay Leeds <cl...@medata.com> on 2004/10/28 19:29:28 UTC
Broken linkmap
NOTE: This post is not in reference to the xml-fop build (for which the
status is still BUILD SUCCESSFUL! ;-)). This is for another
documentation project for my company.
Everything goes normally up until it starts to generate the site
(everything appears to validate, etc.):
====
[..]
------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2004 Apache Software Foundation. All rights reserved.
------------------------------------------------------------------------
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 22 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 36 seconds
[clay@Clay-Leeds-Computer medata_docs]$
====
Steps I've taken to resolve this:
- /forrest clean/
- synchronized forrest.properties & skinconf.xml [1]
I'm able to build my xml-fop, so I don't know why it's not working here.
[1]
http://forrest.apache.org/docs/upgrading_06.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Ross Gardler wrote:
>
>> Nicola Ken Barozzi wrote:
>
> ...
>
>>> I have updated my Forrest, set the new FORREST_HOME, rebuilt, and a
>>> forrest run on the Forrest docs yields the above result.
>>>
>>
>> Fixed - plugins.xml on the webserver had been overwritten with an old
>> version which didn't have the simplified-docbook plugin listed.
>>
>> I've updated the one on the site now.
>
>
> Does it mean that I have to get it from the webserver even if I have the
> plugins on my HD?
No, Forrest will deal with it for you.
Ross
Re: Broken linkmap
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Ross Gardler wrote:
> Nicola Ken Barozzi wrote:
...
>> I have updated my Forrest, set the new FORREST_HOME, rebuilt, and a
>> forrest run on the Forrest docs yields the above result.
>>
>
> Fixed - plugins.xml on the webserver had been overwritten with an old
> version which didn't have the simplified-docbook plugin listed.
>
> I've updated the one on the site now.
Does it mean that I have to get it from the webserver even if I have the
plugins on my HD?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Nicola Ken Barozzi wrote:
> Clay Leeds wrote:
> ...
>
>> fetch-versioned-plugin:
>> Trying to get "simplified-docbook" plugin version
>> ${version}...
>>
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:128: The following error occurred while executing this line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:131: The following error occurred while executing this line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:107: The following error occurred while executing this line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:120: The following error occurred while executing this line:
>> /Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
>> pluginlist2fetchbuild.xml:7: java.net.MalformedURLException: no
>> protocol: simplified-docbook-${version}.zip
>>
>> Total time: 13 seconds
>
>
> I get the same error.
>
> I have updated my Forrest, set the new FORREST_HOME, rebuilt, and a
> forrest run on the Forrest docs yields the above result.
>
Fixed - plugins.xml on the webserver had been overwritten with an old
version which didn't have the simplified-docbook plugin listed.
I've updated the one on the site now.
Ross
Re: Broken linkmap
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Clay Leeds wrote:
...
> fetch-versioned-plugin:
> Trying to get "simplified-docbook" plugin version
> ${version}...
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:128: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:131: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:107: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:120: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
> pluginlist2fetchbuild.xml:7: java.net.MalformedURLException: no
> protocol: simplified-docbook-${version}.zip
>
> Total time: 13 seconds
I get the same error.
I have updated my Forrest, set the new FORREST_HOME, rebuilt, and a
forrest run on the Forrest docs yields the above result.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Nov 3, 2004, at 8:03 PM, David Crossley wrote:
> Clay Leeds wrote:
>> Ross Gardler wrote:
>>> Clay Leeds wrote:
>>>> Clay Leeds wrote:
>>>>> I'll try those steps and see what I can come up with.
>>>> After trying those steps, I was plagued by problems with my install
>>>> of apache-forrest-0.6/ and then with problems related to the Online
>>>> DTDs broken[1]. In any case, I have achieved a BUILD SUCCESSFUL for
>>>> my medata_docs/ project.
>>>
>>> That's the good news.
>>>
>>> Unfortunately I've been really busy elsewhere for a couple of days
>>> and
>>> I didn't follow that thread [1] as I got the impression it was a
>>> problem with the restructuring rather than with the plugin. Do I need
>>> to go back and read that thread - in other words did plugins have
>>> anything to do with the problem?
>>>
>>> Ross
>>
>> Yes.
>
> Hold on. Your issue with "linkmap-linkmap.html" was
> happening prior to the recent hiccup with the skinconf DTD
> (which is fixed now). So i do not think that they are related.
Whatever it is, I'm not getting that error any more when I do a
/forrest/ run with medata_docs/. I've got other problems with xml-fop/
but they don't appear to be related to linkmap...
>> There are some important notes regarding Forrest Documentation
>> that were directed at the dev@f.a.o team. Unfortunately, I've found
>> that 'thread' links on http://issues.apache.org/ don't work correctly
>> (it gives a proper list of thread messages, but the links aren't
>> correct). Here's my most recent POST:
>>
>> http://issues.apache.org/eyebrowse/ReadMsg?
>> listName=dev@forrest.apache.org&msgNo=15200
>
> Better to use http://marc.theaimsgroup.com/ until Apache
> fix that Eyebrowse threading. BTW i have long ago asked
> MARC to add user@f.a.o list. They have hardware troubles
> and told me they would get to it soon.
I see you were following the general@ thread? ;-) Sometimes it can be a
chore to explain what seems so simple. I think I've gotten through,
although it is probably a moot point.
> --
> David Crossley
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> Ross Gardler wrote:
> > Clay Leeds wrote:
> >> Clay Leeds wrote:
> >>>
> >>> I'll try those steps and see what I can come up with.
> >> After trying those steps, I was plagued by problems with my install
> >> of apache-forrest-0.6/ and then with problems related to the Online
> >> DTDs broken[1]. In any case, I have achieved a BUILD SUCCESSFUL for
> >> my medata_docs/ project.
> >
> > That's the good news.
> >
> > Unfortunately I've been really busy elsewhere for a couple of days and
> > I didn't follow that thread [1] as I got the impression it was a
> > problem with the restructuring rather than with the plugin. Do I need
> > to go back and read that thread - in other words did plugins have
> > anything to do with the problem?
> >
> > Ross
>
> Yes.
Hold on. Your issue with "linkmap-linkmap.html" was
happening prior to the recent hiccup with the skinconf DTD
(which is fixed now). So i do not think that they are related.
> There are some important notes regarding Forrest Documentation
> that were directed at the dev@f.a.o team. Unfortunately, I've found
> that 'thread' links on http://issues.apache.org/ don't work correctly
> (it gives a proper list of thread messages, but the links aren't
> correct). Here's my most recent POST:
>
> http://issues.apache.org/eyebrowse/ReadMsg?
> listName=dev@forrest.apache.org&msgNo=15200
Better to use http://marc.theaimsgroup.com/ until Apache
fix that Eyebrowse threading. BTW i have long ago asked
MARC to add user@f.a.o list. They have hardware troubles
and told me they would get to it soon.
--
David Crossley
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Nov 3, 2004, at 11:58 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> Update on broken linkmap/Online DTDs broken problem reported[1] on
>> DEV@f.a.o:
>> On Oct 29, 2004, at 1:05 PM, Clay Leeds wrote:
>>> On Oct 29, 2004, at 12:40 PM, Ross Gardler wrote:
>>>
>>>> Clay Leeds wrote:
>>>>
>>>>> I guess It's possible I have a problem in my medata_docs/
>>>>> project... I don't know what it could be.
>>>>
>>>>
>>>> I'm almost certain of it, but since I am bug-fixing the plugins
>>>> right now I want to make sure. Here's what we need to do:
>>>>
>>>> - cd forrestcore
>>>> - rm -Rf plugins
>>>> - ./build.sh
>>>> - cd [some temporary directory]
>>>> - forrest seed
>>>> - forrest site (or just forrest as you rightly point out)
>>>> - Does it build (with errors about cwiki and ihtml pages)
>>>> - svn up (yes again, I just submitted another fix)
>>>> - check at revision 55988
>>>> - forrst site
>>>> - Does is build without errors
>>>>
>>>> If everything goes as describe we *know* the problem is with your
>>>> site.
>>>
>>>
>>> I'll try those steps and see what I can come up with.
>> After trying those steps, I was plagued by problems with my install
>> of apache-forrest-0.6/ and then with problems related to the Online
>> DTDs broken[1]. In any case, I have achieved a BUILD SUCCESSFUL for
>> my medata_docs/ project.
>
> That's the good news.
>
> Unfortunately I've been really busy elsewhere for a couple of days and
> I didn't follow that thread [1] as I got the impression it was a
> problem with the restructuring rather than with the plugin. Do I need
> to go back and read that thread - in other words did plugins have
> anything to do with the problem?
>
> Ross
Yes. There are some important notes regarding Forrest Documentation
that were directed at the dev@f.a.o team. Unfortunately, I've found
that 'thread' links on http://issues.apache.org/ don't work correctly
(it gives a proper list of thread messages, but the links aren't
correct). Here's my most recent POST:
http://issues.apache.org/eyebrowse/ReadMsg?
listName=dev@forrest.apache.org&msgNo=15200
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> Update on broken linkmap/Online DTDs broken problem reported[1] on
> DEV@f.a.o:
>
> On Oct 29, 2004, at 1:05 PM, Clay Leeds wrote:
>
>> On Oct 29, 2004, at 12:40 PM, Ross Gardler wrote:
>>
>>> Clay Leeds wrote:
>>>
>>>> I guess It's possible I have a problem in my medata_docs/
>>>> project... I don't know what it could be.
>>>
>>>
>>> I'm almost certain of it, but since I am bug-fixing the plugins
>>> right now I want to make sure. Here's what we need to do:
>>>
>>> - cd forrestcore
>>> - rm -Rf plugins
>>> - ./build.sh
>>> - cd [some temporary directory]
>>> - forrest seed
>>> - forrest site (or just forrest as you rightly point out)
>>> - Does it build (with errors about cwiki and ihtml pages)
>>> - svn up (yes again, I just submitted another fix)
>>> - check at revision 55988
>>> - forrst site
>>> - Does is build without errors
>>>
>>> If everything goes as describe we *know* the problem is with your site.
>>
>>
>> I'll try those steps and see what I can come up with.
>
>
> After trying those steps, I was plagued by problems with my install of
> apache-forrest-0.6/ and then with problems related to the Online DTDs
> broken[1]. In any case, I have achieved a BUILD SUCCESSFUL for my
> medata_docs/ project.
That's the good news.
Unfortunately I've been really busy elsewhere for a couple of days and I
didn't follow that thread [1] as I got the impression it was a problem
with the restructuring rather than with the plugin. Do I need to go back
and read that thread - in other words did plugins have anything to do
with the problem?
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
Update on broken linkmap/Online DTDs broken problem reported[1] on
DEV@f.a.o:
On Oct 29, 2004, at 1:05 PM, Clay Leeds wrote:
> On Oct 29, 2004, at 12:40 PM, Ross Gardler wrote:
>> Clay Leeds wrote:
>>> I guess It's possible I have a problem in my medata_docs/ project...
>>> I don't know what it could be.
>>
>> I'm almost certain of it, but since I am bug-fixing the plugins right
>> now I want to make sure. Here's what we need to do:
>>
>> - cd forrestcore
>> - rm -Rf plugins
>> - ./build.sh
>> - cd [some temporary directory]
>> - forrest seed
>> - forrest site (or just forrest as you rightly point out)
>> - Does it build (with errors about cwiki and ihtml pages)
>> - svn up (yes again, I just submitted another fix)
>> - check at revision 55988
>> - forrst site
>> - Does is build without errors
>>
>> If everything goes as describe we *know* the problem is with your
>> site.
>
> I'll try those steps and see what I can come up with.
After trying those steps, I was plagued by problems with my install of
apache-forrest-0.6/ and then with problems related to the Online DTDs
broken[1]. In any case, I have achieved a BUILD SUCCESSFUL for my
medata_docs/ project.
[1] dev@forrest.apache.org post
http://issues.apache.org/eyebrowse/BrowseList?
listName=dev@forrest.apache.org&by=thread&from=920814
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 12:40 PM, Ross Gardler wrote:
> Clay Leeds wrote:
>> On Oct 29, 2004, at 12:11 PM, Ross Gardler wrote:
>>> Your notes did not show you *building* the site (i.e. forrest site)
>>> - sorry I should have been clearer.
>
> Hehe, we are both getting confused now. I was referring to building
> the freshly seeded site - not your custom site - I am trying to make
> sure the problem is not with Forrest itself (which is my current
> suspicion)
See my more recent post. I guess I anticipated that so I tried it with
xml-fop and got a BUILD SUCCESSFUL.
>> I guess It's possible I have a problem in my medata_docs/ project...
>> I don't know what it could be.
>
> I'm almost certain of it, but since I am bug-fixing the plugins right
> now I want to make sure. Here's what we need to do:
>
> - cd forrestcore
> - rm -Rf plugins
> - ./build.sh
> - cd [some temporary directory]
> - forrest seed
> - forrest site (or just forrest as you rightly point out)
> - Does it build (with errors about cwiki and ihtml pages)
> - svn up (yes again, I just submitted another fix)
> - check at revision 55988
> - forrst site
> - Does is build without errors
>
> If everything goes as describe we *know* the problem is with your site.
I'll try those steps and see what I can come up with.
>> [OT]
>> On a side note I notice in my seed4/ site, that there's no
>> OpenOffice.org sample (my seed3/ site does have it). I assume this
>> has something to do with OpenOffice.org moving to a plugin, but I
>> think it would be a travesty (perhaps that's too strong a word...
>> ;-)) to not include an OpenOffice.org sample (and for that matter a
>> Simplified-Docbook sample) in the /forrest seed/ output. Could the
>> plugin automatically add this when doing a /forrest seed/?
>
> We cannot include a working sample since the functionality will not be
> there. What I will be doing as soon as I iron out these bugs is
> creating a page in the seeded site from plugins.xml descriptor which
> describes all plugins, their functionlaity, their status etc.
>
> In the main docs there will be a full demonstration (and I suppose the
> plugins page in a seed site should link back to the relevant section
> on the main site).
>
> Do you think this is enough?
Sounds like it's the best we can do, considering plugins/ are somewhat
out of the scope of the new, improved, leaner/meaner (not to mention
gentler) forrest. I'll chalk that up to a 'Wouldn't it be nice?' and
leave it at that. My point
BTW, putting a real example on the site is even better than (IMHO) what
we currently have. What we currently have is a description of what you
can do, without an actual example (for the example, you *have* to look
in the /forrest seed/ site (or generate your own).
> Ross
[1]
http://forrest.apache.org/docs/oowriter.html
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> FWIW, I just applied all changes I could from the skinconf.xml from
> another project (xml-fop) and it still gives me the 'linkmap' BUILD FAILED.
Well, I'm off to build some furniture now, 'll check back with you
tomorrow, at least I know it is not the plugins that are causing the
problem. No help to you I know, but at least I'm not worrying that I
introduced another bug.
>
> [OT]
> On a similar note, I thought you'd like to know that xml-fop still
> achieves a BUILD SUCCESSFUL :-p
Thanks for that - it is encouraging - very thoughtful of you ;-)
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
FWIW, I just applied all changes I could from the skinconf.xml from
another project (xml-fop) and it still gives me the 'linkmap' BUILD
FAILED.
[OT]
On a similar note, I thought you'd like to know that xml-fop still
achieves a BUILD SUCCESSFUL :-p (Of course I am still working to figure
out the CRITICAL issues with that site's rather complicated Compliance
& other pages...):
====
Total time: 4 minutes 26 seconds, Site size: 2,676,828 Site pages: 168
------------------------------
Static site was successfully generated at:
/Users/Shared/_WebDLs/_repos/xml-fop/build/site
------------------------------
BUILD SUCCESSFUL
Total time: 4 minutes 53 seconds
[clay@Clay-Leeds-Computer xml-fop]$
====
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 29, 2004, at 12:11 PM, Ross Gardler wrote:
>
>> Clay Leeds wrote:
>>
>>>> This is the exact same thing that was happening when the plugins
>>>> we breaking things, but that is fixed and you have done an svn up,
>>>> and you don't have a project sitemap that could be causing the
>>>> problem, I'm confused.
>>>
>>> Just to be safe...
>>> 1. Just ran another /svn up/ so I am now at 55985.
>>> (so far today, I think I've /svn up/'d 3-4 times)
>>
>>
>> I just did an SVN up but the changes are in freshsite and docs so
>> they have no impact (only just submitted I think)
>>
>>>> Lets go back to basics.
>>>>
>>>> Can you successfully build a freshly seeded site?
>>>
>>> yes...
>>
>>
>> Your notes did not show you *building* the site (i.e. forrest site) -
>> sorry I should have been clearer.
Hehe, we are both getting confused now. I was referring to building the
freshly seeded site - not your custom site - I am trying to make sure
the problem is not with Forrest itself (which is my current suspicion)
> I guess It's possible I have a problem in my medata_docs/ project... I
> don't know what it could be.
I'm almost certain of it, but since I am bug-fixing the plugins right
now I want to make sure. Here's what we need to do:
- cd forrestcore
- rm -Rf plugins
- ./build.sh
- cd [some temporary directory]
- forrest seed
- forrest site (or just forrest as you rightly point out)
- Does it build (with errors about cwiki and ihtml pages)
- svn up (yes again, I just submitted another fix)
- check at revision 55988
- forrst site
- Does is build without errors
If everything goes as describe we *know* the problem is with your site.
> [OT]
> On a side note I notice in my seed4/ site, that there's no
> OpenOffice.org sample (my seed3/ site does have it). I assume this has
> something to do with OpenOffice.org moving to a plugin, but I think it
> would be a travesty (perhaps that's too strong a word... ;-)) to not
> include an OpenOffice.org sample (and for that matter a
> Simplified-Docbook sample) in the /forrest seed/ output. Could the
> plugin automatically add this when doing a /forrest seed/?
We cannot include a working sample since the functionality will not be
there. What I will be doing as soon as I iron out these bugs is creating
a page in the seeded site from plugins.xml descriptor which describes
all plugins, their functionlaity, their status etc.
In the main docs there will be a full demonstration (and I suppose the
plugins page in a seed site should link back to the relevant section on
the main site).
Do you think this is enough?
Ross
>
> Web Maestro Clay
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 12:11 PM, Ross Gardler wrote:
> Clay Leeds wrote:
>>> This is the exact same thing that was happening when the plugins we
>>> breaking things, but that is fixed and you have done an svn up, and
>>> you don't have a project sitemap that could be causing the problem,
>>> I'm confused.
>> Just to be safe...
>> 1. Just ran another /svn up/ so I am now at 55985.
>> (so far today, I think I've /svn up/'d 3-4 times)
>
> I just did an SVN up but the changes are in freshsite and docs so they
> have no impact (only just submitted I think)
>
>>> Lets go back to basics.
>>>
>>> Can you successfully build a freshly seeded site?
>> yes...
>
> Your notes did not show you *building* the site (i.e. forrest site) -
> sorry I should have been clearer.
I did:
2. ./build.sh
3. BUILD SUCCESSFUL (11 secs)
4. rm plugins/sitemap.xmap
5. [clay@Clay-Leeds-Computer medata_docs]$ forrest
#2 means I 'built' forrest. #5 Means I ran /forrest/ in my
'medata_docs/' directory. Isn't that the same as /forrest site/? In any
case, I just did a /forrest site/ and got:
====
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 20 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 44 seconds
[clay@Clay-Leeds-Computer medata_docs]$
====
> Current status for me (rev 55986) is that it will build with errors
> unrelated to linkmap (that *is* a problem with plugins and I am fixing
> it now)
>
> Ross
I guess It's possible I have a problem in my medata_docs/ project... I
don't know what it could be.
[OT]
On a side note I notice in my seed4/ site, that there's no
OpenOffice.org sample (my seed3/ site does have it). I assume this has
something to do with OpenOffice.org moving to a plugin, but I think it
would be a travesty (perhaps that's too strong a word... ;-)) to not
include an OpenOffice.org sample (and for that matter a
Simplified-Docbook sample) in the /forrest seed/ output. Could the
plugin automatically add this when doing a /forrest seed/?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 29, 2004, at 11:41 AM, Ross Gardler wrote:
>
<snip/>
>> This is the exact same thing that was happening when the plugins we
>> breaking things, but that is fixed and you have done an svn up, and
>> you don't have a project sitemap that could be causing the problem,
>> I'm confused.
>
>
> Just to be safe...
>
> 1. Just ran another /svn up/ so I am now at 55985.
> (so far today, I think I've /svn up/'d 3-4 times)
I just did an SVN up but the changes are in freshsite and docs so they
have no impact (only just submitted I think)
>> Lets go back to basics.
>>
>> Can you successfully build a freshly seeded site?
>
>
> yes...
Your notes did not show you *building* the site (i.e. forrest site) -
sorry I should have been clearer.
Current status for me (rev 55986) is that it will build with errors
unrelated to linkmap (that *is* a problem with plugins and I am fixing
it now)
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 11:41 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> On Oct 29, 2004, at 11:14 AM, Ross Gardler wrote:
>>> Clay Leeds wrote:
>>>> On Oct 29, 2004, at 10:21 AM, Ross Gardler wrote:
>>>>> Now that we have that out of the way lets return to your linkmap
>>>>> problem. Can you confirm that when you run without plugins enabled
>>>>> (deleting forrestcore/plugins/sitemap.xmap) you still get the
>>>>> same problem.
>>>>
>>>> Running now... (twiddling for 36-40 seconds...) and... drumroll
>>>> please... "D'oh!"
>>>> X [0] linkmap.html BROKEN: No
>>>> pipeline matched request: linkmap-linkmap.html
>>>> Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
>>>> BUILD FAILED
>>>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>>>> site.xml:43: Java returned: 1
>>>> Total time: 38 seconds
>>>> [clay@Clay-Leeds-Computer medata_docs]$
>>>
>>> So it isn't the plugins (since they are not being loaded if you
>>> deleted forrestcore/plugins/sitemap.xmap (you didn't do a ./build.sh
>>> did you? - this would rebuild the plugins sitemap).
>> I did a './build.sh' from forrestcore/ and then 'rm
>> plugins/sitemap.xmap' before I did that BUILD FAILED...
>
> OK, that is what I wanted.
>
>>> What does brokenlinks.xml say?
>> <broken-links>
>> <link RENAME_FILE_TO_USE_message="No pipeline matched request:
>> linkmap-linkmap.html" uri="linkmap.html">
>> </link>
>> </broken-links>
>
> This is the exact same thing that was happening when the plugins we
> breaking things, but that is fixed and you have done an svn up, and
> you don't have a project sitemap that could be causing the problem,
> I'm confused.
Just to be safe...
1. Just ran another /svn up/ so I am now at 55985.
(so far today, I think I've /svn up/'d 3-4 times)
2. ./build.sh
3. BUILD SUCCESSFUL (11 secs)
4. rm plugins/sitemap.xmap
5. [clay@Clay-Leeds-Computer medata_docs]$ forrest
6. [..]
7. X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 20 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 38 seconds
8. D'oh!
> Lets go back to basics.
>
> Can you successfully build a freshly seeded site?
yes...
[clay@Clay-Leeds-Computer temp]$ mkdir seed4
[clay@Clay-Leeds-Computer temp]$ cd seed4
[clay@Clay-Leeds-Computer seed4]$ forrest seed
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/
forrest.build.xml
init-props:
Loading project specific properties from
/Users/Shared/_WebDLs/_repos/temp/seed4/forrest.properties
Loading user specific properties from /Users/clay/forrest.properties
Loading default properties from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/context/
default-forrest.properties
Created dir: /Users/Shared/_WebDLs/_repos/temp/seed4/build/tmp
echo-settings:
check-contentdir:
ensure-nocontent:
seed:
Copying 45 files to /Users/Shared/_WebDLs/_repos/temp/seed4
-------------------------------
~~ Template project created! ~~
Here is an outline of the generated files:
/ # /Users/Shared/_WebDLs/_repos/temp/seed4
/status.xml # List of project developers, todo list and
change log
/forrest.properties # Optional file describing your site layout
/src/documentation/ # Doc-specific files
/src/documentation/skinconf.xml # Info about your project used by
the skin
/src/documentation/content/ # Site content.
/src/documentation/content/xdocs # XML content.
/src/documentation/content/xdocs/index.xml # Home page
/src/documentation/content/xdocs/site.xml # Navigation file for site
structure
/src/documentation/content/xdocs/tabs.xml # Skin-specific 'tabs' file.
/src/documentation/content/*.html,pdf # Static content files, may have
subdirs
/src/documentation/resources/images # Project images (logos, etc)
# you can create other directories as needed (see forrest.properties)
What to do now?
- Render this template to static HTML by typing 'forrest'.
View the generated HTML in a browser to make sure everything works.
- Alternatively 'forrest run' and browse to http://localhost:8888/ live
demo.
- Edit status.xml and src/documentation/skinconf.xml
to customize for your project.
- Start adding content in xdocs/ remembering to declare new files in
site.xml
- Follow the document http://forrest.apache.org/docs/your-project.html
- Provide any feedback to dev@forrest.apache.org
Thanks for using Apache Forrest
-------------------------------
BUILD SUCCESSFUL
Total time: 8 seconds
[clay@Clay-Leeds-Computer seed4]$
> If you do Forrest run on the project that is failing above what
> happens (remember with the plugins disabled your OpenOffice.org stuff
> will not work).
Sorry... was that a /forrest run/ or a /forrest/ run? (gets confusing!).
Anyway, I did a /forrest/ run and received a... drumroll please...
waiting... it got past the linkmap BROKEN thingamajig...
====
Total time: 2 minutes 4 seconds, Site size: 438,770 Site pages: 58
------------------------------
Static site was successfully generated at:
/Users/Shared/_WebDLs/_repos/temp/seed4/build/site
------------------------------
BUILD SUCCESSFUL
Total time: 2 minutes 24 seconds
====
That works...
<grasping-at-straws>
Perhaps there's something wrong with my site.xml:
====
[clay@Clay-Leeds-Computer medata_docs]$ find . -iname *site*
./build/site
./build/webapp/WEB-INF/logs/sitemap.log
./src/documentation/content/xdocs/site.xml
[clay@Clay-Leeds-Computer medata_docs]$
====
</grasping-at-straws>
Could it be a skinconf.xml or forrest.properties issue?
>>> Is there any relevant info in WEB-INF/logs?
>
> Well I was clutching at straws and that was certainly the shortest!
>
> Ross
Heh! At least I've got got my sense of humor, ¿no?
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 29, 2004, at 11:14 AM, Ross Gardler wrote:
>
>> Clay Leeds wrote:
>>
>>> On Oct 29, 2004, at 10:21 AM, Ross Gardler wrote:
>>>
>>>> Now that we have that out of the way lets return to your linkmap
>>>> problem. Can you confirm that when you run without plugins enabled
>>>> (deleting forrestcore/plugins/sitemap.xmap) you still get the same
>>>> problem.
>>>
>>> Running now... (twiddling for 36-40 seconds...) and... drumroll
>>> please... "D'oh!"
>>> X [0] linkmap.html BROKEN: No
>>> pipeline matched request: linkmap-linkmap.html
>>> Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
>>> BUILD FAILED
>>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>>> site.xml:43: Java returned: 1
>>> Total time: 38 seconds
>>> [clay@Clay-Leeds-Computer medata_docs]$
>>
>>
>> So it isn't the plugins (since they are not being loaded if you
>> deleted forrestcore/plugins/sitemap.xmap (you didn't do a ./build.sh
>> did you? - this would rebuild the plugins sitemap).
>
>
> I did a './build.sh' from forrestcore/ and then 'rm
> plugins/sitemap.xmap' before I did that BUILD FAILED...
OK, that is what I wanted.
>> What does brokenlinks.xml say?
>
>
> <broken-links>
> <link message="No pipeline matched request: linkmap-linkmap.html"
> uri="linkmap.html">
> </link>
> </broken-links>
This is the exact same thing that was happening when the plugins we
breaking things, but that is fixed and you have done an svn up, and you
don't have a project sitemap that could be causing the problem, I'm
confused.
Lets go back to basics.
Can you successfully build a freshly seeded site?
If you do Forrest run on the project that is failing above what happens
(remember with the plugins disabled your OpenOffice.org stuff will not
work).
>
>> Is there any relevant info in WEB-INF/logs?
Well I was clutching at straws and that was certainly the shortest!
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 11:14 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> On Oct 29, 2004, at 10:21 AM, Ross Gardler wrote:
>>> Now that we have that out of the way lets return to your linkmap
>>> problem. Can you confirm that when you run without plugins enabled
>>> (deleting forrestcore/plugins/sitemap.xmap) you still get the same
>>> problem.
>> Running now... (twiddling for 36-40 seconds...) and... drumroll
>> please... "D'oh!"
>> X [0] linkmap.html BROKEN: No
>> pipeline matched request: linkmap-linkmap.html
>> Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> site.xml:43: Java returned: 1
>> Total time: 38 seconds
>> [clay@Clay-Leeds-Computer medata_docs]$
>
> So it isn't the plugins (since they are not being loaded if you
> deleted forrestcore/plugins/sitemap.xmap (you didn't do a ./build.sh
> did you? - this would rebuild the plugins sitemap).
I did a './build.sh' from forrestcore/ and then 'rm
plugins/sitemap.xmap' before I did that BUILD FAILED...
> What does brokenlinks.xml say?
<broken-links>
<link message="No pipeline matched request: linkmap-linkmap.html"
uri="linkmap.html">
</link>
</broken-links>
> Is there any relevant info in WEB-INF/logs?
Which one(s) should I look at (I'm guessing error.log is a good
candidate ;-))? I don't know what to look for, but:
[clay@Clay-Leeds-Computer medata_docs]$ ls -l build/webapp/WEB-INF/logs/
total 592
-rw-rw-rw- 1 clay 0 Oct 28 10:05 access.log
-rw-rw-rw- 1 clay 3343 Oct 29 11:01 core.log
-rw-rw-rw- 1 clay 596866 Oct 29 11:00 debug.log
-rw-rw-rw- 1 clay 856 Oct 29 11:00 error.log
-rw-rw-rw- 1 clay 0 Oct 28 10:05 flow.log
-rw-rw-rw- 1 clay 0 Oct 28 10:05 idgen.log
-rw-rw-rw- 1 clay 0 Oct 28 10:05 linkrewriter.log
-rw-rw-rw- 1 clay 0 Oct 28 10:05 sitemap.log
-rw-rw-rw- 1 clay 0 Oct 28 10:05 xmlform.log
error.log:
ERROR (2004-10-29) 11:00.52:719
[org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache] (Unknown-URI)
Unknown-thread/LogKitLogger: Failure updating element, cacheName: main,
key:
PK_G-file-file:/Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
build-info.xml
java.lang.InterruptedException
at
EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLoc
k.acquire(Unknown Source)
at
org.apache.jcs.auxiliary.disk.indexed.IndexedDiskCache.doUpdate(IndexedD
iskCache.java:362)
at
org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePu
t(AbstractDiskCache.java:441)
at
org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.jav
a:573)
at
org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQ
ueue.java:489)
at
org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.jav
a:461)
> (I'm currently at a loss with this, so I'm looking for clues at
> "random")
>
> Ross
FWIW here're the contents of /medata_docs/build/tmp/build-info.xml:
<info>
<project-skin>pelt</project-skin>
<forrest-version>0.7-dev</forrest-version>
</info>
(but you probably knew that ;-))
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 29, 2004, at 10:21 AM, Ross Gardler wrote:
>
>> Now that we have that out of the way lets return to your linkmap
>> problem. Can you confirm that when you run without plugins enabled
>> (deleting forrestcore/plugins/sitemap.xmap) you still get the same
>> problem.
>
>
> Running now... (twiddling for 36-40 seconds...) and... drumroll
> please... "D'oh!"
>
> X [0] linkmap.html BROKEN: No
> pipeline matched request: linkmap-linkmap.html
> Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> site.xml:43: Java returned: 1
>
> Total time: 38 seconds
> [clay@Clay-Leeds-Computer medata_docs]$
>
So it isn't the plugins (since they are not being loaded if you deleted
forrestcore/plugins/sitemap.xmap (you didn't do a ./build.sh did you? -
this would rebuild the plugins sitemap).
What does brokenlinks.xml say?
Is there any relevant info in WEB-INF/logs?
(I'm currently at a loss with this, so I'm looking for clues at "random")
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 10:21 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> On Oct 29, 2004, at 6:49 AM, Ross Gardler wrote:
>>> Clay Leeds wrote:
>>
>> I just deleted forrestcore/plugins/sitemap.xmap and ran /forrest/:
>> X [0] linkmap.html BROKEN: No
>> pipeline matched request: linkmap-linkmap.html
>> Total time: 0 minutes 22 seconds, Site size: 0 Site pages: 0
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> site.xml:43: Java returned: 1
>> Total time: 41 seconds
>> [clay@Clay-Leeds-Computer medata_docs]$
>> so I'm assuming it's with the plugins...
>
> No this means it is *not* the plugins since none of them are being
> loaded.
<snip>
>>> If you have an application that worked in 0.6 you can still use
>>> 0.7-dev with no changes to your forrest.properties file since the
>>> default behaviour is to include all plugins that contain
>>> functionality extracted from the 0.6 release. In other words the
>>> developer need do nothing unless they want to use new functionality
>>> provided by new plugins.
>> That would be true, except in my case all of my files are
>> OpenOffice.org files...
>
> No, you misunderstand. If you don't add a project.required.plugins
> property it will *automatically* load the simplified-Docbook and
> OpenOffice.org plugins. You don't have to do anything if you want to
> maintain compatability with 0.6.
>
> (I've clarified this in the docs in SVN alread)
OK... That is good to know. Oh what a a tangled web we weave...
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:128: The following error occurred while executing this
>> line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:131: The following error occurred while executing this
>> line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:107: The following error occurred while executing this
>> line:
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> plugins.xml:120: The following error occurred while executing this
>> line:
>> /Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
>> pluginlist2fetchbuild.xml:7: java.net.MalformedURLException: no
>> protocol: simplified-docbook-${version}.zip
>
> As mentioned in another post, this is fixed. This was caused by a
> glitch in the site updating process that meant a change in SVN was not
> reflected on the published site. Result was that an old version of
> plugins.xml was published. This won't happen again as the glitch has
> been removed.
Just ran again, after commenting out the project.required.plugins
entry. Still "D'oh!".
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 40 seconds
[clay@Clay-Leeds-Computer medata_docs]$
> Now that we have that out of the way lets return to your linkmap
> problem. Can you confirm that when you run without plugins enabled
> (deleting forrestcore/plugins/sitemap.xmap) you still get the same
> problem.
Running now... (twiddling for 36-40 seconds...) and... drumroll
please... "D'oh!"
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 38 seconds
[clay@Clay-Leeds-Computer medata_docs]$
> If you do then it is nothing to do with the plugins, it is something
> else causing it.
>
>> Funny thing is, I'm not using anything besides OpenOffice.org files,
>> so why is it complaining about simplified-docbook? For that matter,
>> why does it download IMSManifest?
>
> Does the above autoloading explanation make sense now?
>
> Ross
Makes sense! (Still "D'oh!" ;-)) Glad I have 'help'!
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 29, 2004, at 6:49 AM, Ross Gardler wrote:
>
>> Clay Leeds wrote:
>>
> I just deleted forrestcore/plugins/sitemap.xmap and ran /forrest/:
>
> X [0] linkmap.html BROKEN: No
> pipeline matched request: linkmap-linkmap.html
> Total time: 0 minutes 22 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> site.xml:43: Java returned: 1
>
> Total time: 41 seconds
> [clay@Clay-Leeds-Computer medata_docs]$
>
> so I'm assuming it's with the plugins...
No this means it is *not* the plugins since none of them are being loaded.
>> "If a site requires a plugin then it will be named in the
>> project.required.plugins property in the projects forrest.properties
>> file. When Forrest builds the site it will automatically discover the
>> plugin and install it. In other words, the user need do nothing."
>
>
> Unfortunately, it doesn't indicate what the actual line should look
> like in forrest.properties:
>
> project.required.plugins=openOffice.org
>
> [OT forrest.properties example]
> (IMO, every time a forrest.properties 'property' is discussed in the
> Forrest Docs, there should be an example showing possible 'known'
> values and an example of the proper way to add the line--also, I don't
> know if it matters 'where' a property is placed, but if so, there
> should be a mention of this.)
Good point, I'll fix in the plugins docs.
>> If you have an application that worked in 0.6 you can still use
>> 0.7-dev with no changes to your forrest.properties file since the
>> default behaviour is to include all plugins that contain
>> functionality extracted from the 0.6 release. In other words the
>> developer need do nothing unless they want to use new functionality
>> provided by new plugins.
>
>
> That would be true, except in my case all of my files are
> OpenOffice.org files...
No, you misunderstand. If you don't add a project.required.plugins
property it will *automatically* load the simplified-Docbook and
OpenOffice.org plugins. You don't have to do anything if you want to
maintain compatability with 0.6.
(I've clarified this in the docs in SVN alread)
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:128: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:131: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:107: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> plugins.xml:120: The following error occurred while executing this line:
> /Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
> pluginlist2fetchbuild.xml:7: java.net.MalformedURLException: no
> protocol: simplified-docbook-${version}.zip
As mentioned in another post, this is fixed. This was caused by a glitch
in the site updating process that meant a change in SVN was not
reflected on the published site. Result was that an old version of
plugins.xml was published. This won't happen again as the glitch has
been removed.
Now that we have that out of the way lets return to your linkmap
problem. Can you confirm that when you run without plugins enabled
(deleting forrestcore/plugins/sitemap.xmap) you still get the same problem.
If you do then it is nothing to do with the plugins, it is something
else causing it.
> Funny thing is, I'm not using anything besides OpenOffice.org files, so
> why is it complaining about simplified-docbook? For that matter, why
> does it download IMSManifest?
Does the above autoloading explanation make sense now?
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 29, 2004, at 6:49 AM, Ross Gardler wrote:
> Clay Leeds wrote:
>> Whole site capability was still in there. I disabled it, and I still
>> get:
>> ====
>> X [0] linkmap.html BROKEN: No
>> pipeline matched request: linkmap-linkmap.html
>> Total time: 0 minutes 18 seconds, Site size: 0 Site pages: 0
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> site.xml:43: Java returned: 1
>> Total time: 37 seconds
>> ====
>
> Do you have a project sitemap? It may be that that is causing the
> problem. You can test this by deleting the
> forrestcore/plugins/sitemap.xmap file. This will prevent Forrest from
> using any plugins. If there error goes away then the problem is with
> your projects sitemap.xmap, if it doesn't it is with the plugins. Let
> me know which way around it is.
FWIW:
[clay@Clay-Leeds-Computer medata_docs]$ find . -iname *sitemap*
./build/webapp/WEB-INF/logs/sitemap.log
[clay@Clay-Leeds-Computer medata_docs]$
I just deleted forrestcore/plugins/sitemap.xmap and ran /forrest/:
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 22 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 41 seconds
[clay@Clay-Leeds-Computer medata_docs]$
so I'm assuming it's with the plugins...
> [NB, in once this test is done you will need to delete the whole
> forrestcore/plugins directory and rebuild Forrest to re-enable the
> plugins functionality]
BTW, before I deleted it, I ls'd my plugins/ directory and got:
[clay@Clay-Leeds-Computer plugins]$ ls
openOffice.org plugins-1.xml simplified-docbook sitemap.xmap.old
OpenOffice.org should have an initial cap 'OpenOffice.org'
[OT I just ran 'NB' through my nifty little 'wtf' utility (nice,
huh!?), and didn't come up with anything... At first I though NB was
short for Nikola Ken Barozzi (sp?)]
[clay@Clay-Leeds-Computer plugins]$ wtf NB
Gee... I don't know what NB means...
[clay@Clay-Leeds-Computer plugins]$ wtf AFAIK
AFAIK: as far as I know
[clay@Clay-Leeds-Computer plugins]$
>> One thing I should mention (and this is almost certainly related to
>> the problem :-)) is that this site consists almost exclusively of
>> OpenOffice.org sxw files (except for the 'index.html' pages), and I
>> have not done anything to configure the plugins yet (other than /svn
>> up/ I have not installed any plugins).
>
> I don't think this is related since the error has nothing to do with
> openOffice documents.
Well... I've got a different error now. I'll post it below...
>> I'm still a bit unclear on how to do that (I'll dig through my ML
>> archives for clues...).
>
> I'd recommend reading the docs, it's more efficient ;-). see "How to
> install plugins" -
> http://forrest.apache.org/docs/
> plugins.html#How+is+a+Plugin+Installed%3F
>
> Since it is only two lines (and the other job I have this morning is
> building furniture), I'll be nice and copy the relevant bit here:
>
> "If a site requires a plugin then it will be named in the
> project.required.plugins property in the projects forrest.properties
> file. When Forrest builds the site it will automatically discover the
> plugin and install it. In other words, the user need do nothing."
Unfortunately, it doesn't indicate what the actual line should look
like in forrest.properties:
project.required.plugins=openOffice.org
[OT forrest.properties example]
(IMO, every time a forrest.properties 'property' is discussed in the
Forrest Docs, there should be an example showing possible 'known'
values and an example of the proper way to add the line--also, I don't
know if it matters 'where' a property is placed, but if so, there
should be a mention of this.)
> (not in the docs, but relevant - so I'll put in the docs now)
>
> If you have an application that worked in 0.6 you can still use
> 0.7-dev with no changes to your forrest.properties file since the
> default behaviour is to include all plugins that contain functionality
> extracted from the 0.6 release. In other words the developer need do
> nothing unless they want to use new functionality provided by new
> plugins.
That would be true, except in my case all of my files are
OpenOffice.org files...
> [NB if you delete the plugins directory as described above, rebuild
> forrest and do a forrest run (or site) you should see in the output
> that Forrest is downloading and installing the required plugins]
Saw that! Bitchin!
>> If that is the problem (missing OOo plugin), it may make sense to
>> create some sort of error which indicates such (something like "No
>> plugin was found which supports the '*.sxw' format needed to process
>> file 'yatayata.sxw'").
>
> If for any reason the plugin was not available Cocoon would complain
> about no match found for yatayata.sxw.
>
> Ross
====
[clay@Clay-Leeds-Computer medata_docs]$ forrest
Apache Forrest. Run 'forrest -projecthelp' to list options
Buildfile:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/
forrest.build.xml
init-props:
Loading project specific properties from
/Users/Shared/_WebDLs/_repos/medata_docs/forrest.properties
Loading user specific properties from /Users/clay/forrest.properties
Loading default properties from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/context/
default-forrest.properties
echo-settings:
check-skin:
fetch-skins-descriptors:
fetch-skin:
unpack-skins:
init-skins:
install-required-plugins:
Installing plugin: openOffice.org
check-plugin:
init-props:
Loading project specific properties from
/Users/Shared/_WebDLs/_repos/medata_docs/forrest.properties
Loading user specific properties from /Users/clay/forrest.properties
Loading default properties from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/context/
default-forrest.properties
echo-settings:
fetch-plugins-descriptors:
fetching descriptor: http://forrest.apache.org/plugins/plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
.
last modified = Fri Oct 29 06:25:12 PDT 2004
fetch-plugin:
Processing
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/plugins-1.xml
to
/Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
pluginlist2fetchbuild.xml
Loading stylesheet
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/var/
pluginlist2fetch.xsl
fetch-versioned-plugin:
Trying to get "openOffice.org" plugin version
${version}...
Getting:
http://www.apache.org/~rgardler/testingGround/forrestPlugins/
openOffice.org-${version}.zip
Error opening connection java.io.IOException
Error opening connection java.io.IOException
Error opening connection java.io.IOException
Can't get
http://www.apache.org/~rgardler/testingGround/forrestPlugins/
openOffice.org-${version}.zip to
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/
openOffice.org.zip
fetch-unversioned-plugin:
Versioned plugin unavailable, trying to get versionless plugin...
Getting:
http://www.apache.org/~rgardler/testingGround/forrestPlugins/
openOffice.org.zip
......................................
last modified = Sat Oct 23 19:21:51 PDT 2004
final-check:
Plugin "openOffice.org" correctly installed.
fetchplugin:
unpack-plugin:
Expanding:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/
openOffice.org.zip into
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins
Deleting 1 files from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins
configure-plugin:
Processing
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/sitemap.xmap
to
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/
sitemap.xmap.new
Loading stylesheet
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/var/
pluginMountSnippet.xsl
Moving 1 files to
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins
Moving 1 files to
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins
install-plugin:
Installing plugin: simplified-docbook
check-plugin:
init-props:
Loading project specific properties from
/Users/Shared/_WebDLs/_repos/medata_docs/forrest.properties
Loading user specific properties from /Users/clay/forrest.properties
Loading default properties from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/context/
default-forrest.properties
echo-settings:
fetch-plugins-descriptors:
Deleting 1 files from
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins
fetching descriptor: http://forrest.apache.org/plugins/plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
.
last modified = Fri Oct 29 06:25:12 PDT 2004
fetch-plugin:
Processing
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/plugins/plugins-1.xml
to
/Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
pluginlist2fetchbuild.xml
Loading stylesheet
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/var/
pluginlist2fetch.xsl
fetch-versioned-plugin:
Trying to get "simplified-docbook" plugin version
${version}...
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
plugins.xml:128: The following error occurred while executing this
line:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
plugins.xml:131: The following error occurred while executing this
line:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
plugins.xml:107: The following error occurred while executing this
line:
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
plugins.xml:120: The following error occurred while executing this
line:
/Users/Shared/_WebDLs/_repos/medata_docs/build/tmp/
pluginlist2fetchbuild.xml:7: java.net.MalformedURLException: no
protocol: simplified-docbook-${version}.zip
Total time: 13 seconds
[clay@Clay-Leeds-Computer medata_docs]$
===
Funny thing is, I'm not using anything besides OpenOffice.org files, so
why is it complaining about simplified-docbook? For that matter, why
does it download IMSManifest?
NOTE: I added the project.required.plugins=openOffice.org
[OpenOffice.org! :-p] line to forrest.properties after I ran the above.
Then I ran another /forrest/ and got another:
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 19 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 35 seconds
[clay@Clay-Leeds-Computer medata_docs]$
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
> On Oct 28, 2004, at 9:37 PM, David Crossley wrote:
>
>> Clay Leeds wrote:
>>
>>> On Oct 28, 2004, at 6:34 PM, Ross Gardler wrote:
>>>
>>>> This will only have affected people working with SVN head. However, it
>>>> is now fixed, please do an svn up and you should be working fine.
>>>>
>>>> Ross
>>>
>>>
>>> I have done an /svn up/ and I still get:
>>> ----------------------------------------------------------------------
>>> --
>>> X [0] linkmap.html BROKEN: No
>>> pipeline matched request: linkmap-linkmap.html
>>> Total time: 0 minutes 30 seconds, Site size: 0 Site pages: 0
>>
>>
>
<snip/>
>
> Whole site capability was still in there. I disabled it, and I still get:
>
> ====
> X [0] linkmap.html BROKEN: No
> pipeline matched request: linkmap-linkmap.html
> Total time: 0 minutes 18 seconds, Site size: 0 Site pages: 0
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> site.xml:43: Java returned: 1
>
> Total time: 37 seconds
> ====
Do you have a project sitemap? It may be that that is causing the
problem. You can test this by deleting the
forrestcore/plugins/sitemap.xmap file. This will prevent Forrest from
using any plugins. If there error goes away then the problem is with
your projects sitemap.xmap, if it doesn't it is with the plugins. Let me
know which way around it is.
[NB, in once this test is done you will need to delete the whole
forrestcore/plugins directory and rebuild Forrest to re-enable the
plugins functionality]
> One thing I should mention (and this is almost certainly related to the
> problem :-)) is that this site consists almost exclusively of
> OpenOffice.org sxw files (except for the 'index.html' pages), and I
> have not done anything to configure the plugins yet (other than /svn
> up/ I have not installed any plugins).
I don't think this is related since the error has nothing to do with
openOffice documents.
> I'm still a bit unclear on how
> to do that (I'll dig through my ML archives for clues...).
I'd recommend reading the docs, it's more efficient ;-). see "How to
install plugins" -
http://forrest.apache.org/docs/plugins.html#How+is+a+Plugin+Installed%3F
Since it is only two lines (and the other job I have this morning is
building furniture), I'll be nice and copy the relevant bit here:
"If a site requires a plugin then it will be named in the
project.required.plugins property in the projects forrest.properties
file. When Forrest builds the site it will automatically discover the
plugin and install it. In other words, the user need do nothing."
(not in the docs, but relevant - so I'll put in the docs now)
If you have an application that worked in 0.6 you can still use 0.7-dev
with no changes to your forrest.properties file since the default
behaviour is to include all plugins that contain functionality extracted
from the 0.6 release. In other words the developer need do nothing
unless they want to use new functionality provided by new plugins.
[NB if you delete the plugins directory as described above, rebuild
forrest and do a forrest run (or site) you should see in the output that
Forrest is downloading and installing the required plugins]
>If that is
> the problem (missing OOo plugin), it may make sense to create some sort
> of error which indicates such (something like "No plugin was found
> which supports the '*.sxw' format needed to process file 'yatayata.sxw'").
If for any reason the plugin was not available Cocoon would complain
about no match found for yatayata.sxw.
Ross
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 28, 2004, at 9:37 PM, David Crossley wrote:
> Clay Leeds wrote:
>> On Oct 28, 2004, at 6:34 PM, Ross Gardler wrote:
>>> This will only have affected people working with SVN head. However,
>>> it
>>> is now fixed, please do an svn up and you should be working fine.
>>>
>>> Ross
>>
>> I have done an /svn up/ and I still get:
>> ----------------------------------------------------------------------
>> --
>> X [0] linkmap.html BROKEN: No
>> pipeline matched request: linkmap-linkmap.html
>> Total time: 0 minutes 30 seconds, Site size: 0 Site pages: 0
>
> These are just wild guesses ...
>
> Do you link explicitly to that "linkmap.html" from your
> site.xml or from other docs? Normally linkmap.html is
> generated because that is the starting point defined by
> default in forrest.properties
>
> Are you attempting to use the broken "whole site" capability?
>
> --
> David Crossley
Whole site capability was still in there. I disabled it, and I still
get:
====
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 18 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 37 seconds
====
One thing I should mention (and this is almost certainly related to the
problem :-)) is that this site consists almost exclusively of
OpenOffice.org sxw files (except for the 'index.html' pages), and I
have not done anything to configure the plugins yet (other than /svn
up/ I have not installed any plugins). I'm still a bit unclear on how
to do that (I'll dig through my ML archives for clues...). If that is
the problem (missing OOo plugin), it may make sense to create some sort
of error which indicates such (something like "No plugin was found
which supports the '*.sxw' format needed to process file
'yatayata.sxw'").
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by David Crossley <cr...@apache.org>.
Clay Leeds wrote:
> On Oct 28, 2004, at 6:34 PM, Ross Gardler wrote:
> > Clay Leeds wrote:
> >> BUILD FAILED
> >> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> >> site.xml:43: Java returned: 1
> >
> > This will only have affected people working with SVN head. However, it
> > is now fixed, please do an svn up and you should be working fine.
> >
> > Ross
>
> I have done an /svn up/ and I still get:
> ------------------------------------------------------------------------
> X [0] linkmap.html BROKEN: No
> pipeline matched request: linkmap-linkmap.html
> Total time: 0 minutes 30 seconds, Site size: 0 Site pages: 0
These are just wild guesses ...
Do you link explicitly to that "linkmap.html" from your
site.xml or from other docs? Normally linkmap.html is
generated because that is the starting point defined by
default in forrest.properties
Are you attempting to use the broken "whole site" capability?
--
David Crossley
Re: Broken linkmap
Posted by Clay Leeds <cl...@medata.com>.
On Oct 28, 2004, at 6:34 PM, Ross Gardler wrote:
> Clay Leeds wrote:
>> BUILD FAILED
>> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
>> site.xml:43: Java returned: 1
>
> This will only have affected people working with SVN head. However, it
> is now fixed, please do an svn up and you should be working fine.
>
> Ross
I have done an /svn up/ and I still get:
------------------------------------------------------------------------
X [0] linkmap.html BROKEN: No
pipeline matched request: linkmap-linkmap.html
Total time: 0 minutes 30 seconds, Site size: 0 Site pages: 0
BUILD FAILED
/Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
site.xml:43: Java returned: 1
Total time: 1 minute 6 seconds
[clay@Clay-Leeds-Computer medata_docs]$
Web Maestro Clay
--
Clay Leeds - <cl...@medata.com>
Webmaster/Developer - Medata, Inc. - <http://www.medata.com/>
PGP Public Key: <https://mail.medata.com/pgp/cleeds.asc>
Re: Broken linkmap
Posted by Ross Gardler <rg...@apache.org>.
Clay Leeds wrote:
>
> BUILD FAILED
> /Users/Shared/_WebDLs/_repos/forrest/forrestcore/src/core/targets/
> site.xml:43: Java returned: 1
>
This will only have affected people working with SVN head. However, it
is now fixed, please do an svn up and you should be working fine.
Ross