Nabble - Apache Forrest - Dev

[jira] Created: (FOR-1130) Please add Newton to list of example sites

2008-11-21T06:44:44Z

Please add Newton to list of example sites
------------------------------------------

Key: FOR-1130
URL: https://issues.apache.org/jira/browse/FOR-1130
Project: Forrest
Issue Type: Task
Components: Example Sites
Reporter: Derek Baum
Priority: Trivial

Please add Newton to the list of example sites.

Name: Newton
URL: http://newton.codecauldron.org
catch-phrase: Distributed OSGi framework

many of the examples on the Newton site are generated from Open Office .odt documents, and much of the site is built into a single PDF developers guide.
We have configured site.xml so the table of contents in the PDF looks reasonable.

Thanks,

Derek

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: FOR-1108 on Mac

2008-11-21T03:06:44Z

On Fri, Nov 21, 2008 at 12:09 AM, David Crossley <crossley@...> wrote:

> Tim Williams wrote:
>> David Crossley wrote:
>> > Tim Williams wrote:
>> >> David Crossley wrote:
>> >> > Tim Williams wrote:
>> >> >> David Crossley wrote:
>> >> >
>> >> > What are the errors that you are seeing?
>> >> >
>> >> >> There is actually a note at the bottom of
>> >> >> /samples-b/linking.html that gives a obscure clue - reading that note
>> >> >> it's still not clear to me why it fails to harshly at this point.
>> >> >
>> >> > That note is attempting to explain that the generated
>> >> > docs (as deployed on the zone) are not at the root of
>> >> > the webserver, hence the generated paths for some of
>> >> > the image references are not showing correctly.
>> >> > I don't understand how that would relate to FOR-1108.
>> >>
>> >> Ok, apologies in advance if I'm missing something incredibly obvious -
>> >> I'm coming from a long hibernation...
>> >>
>> >> So, I'm failing with a NPE just like the attached log file in
>> >> FOR-1108.
>> >
>> > That is not related to FOR-1108. It is something else
>> > that appeared around the same time. It came along with
>> > the upgrade of our PDF output plugin. See the dev archives,
>> > where there is some discussion about it between me and Jeremias.
>>
>> This is bizarre. It was a discussion between you a Jeremias[1] that
>> led me to FOR-1108 because of Ross' concluding mail[2].
>
> That [1] is not the conversation that i was referring to.
> This is it a little further in that thread:
> [3] http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c20080912114226.GD2534@...%3e
>
> There are two separate issues:
>
> *) The one with icon-b and the NPE. See [3] and see
> the first part of the output listing in [1].
>
> *) The crux of FOR-1108, which is the part where
> it fails (only on Windows we thought) with the very
> corrupted path to dataModel.xmap file. See the
> the seconds part of the output listing in [1].
>
> -----------
> X [0] linkmap.html BROKEN: C:\Dev\apache.org\rw\forrest-trunk\main\webapp\.\C:\Dev\apache.org\rw\forrest-trunk\build\test_d
> ispatcher_site\build\tmp\C:\Dev\apache.org\rw\forrest-trunk\build\plugins\dataModel.xmap
> -----------
>
> So are you seeing a similarly corrupted path too?

I'm not sure, I've been seeing exactly what's in the log about icon-b
and NPE, I'll have to look this evening and see if I see the other
one.

--tim

Re: [jira] Updated: (FOR-1005) Use sourcetypeaction for input plugins

2008-11-21T02:21:42Z

Daive, I agree that this is a good entry level issue. I wonder if we
should have a page on the site that highlights these entry level issues
with a big notice saying our devs are happy to help people understand
the steps needed. I'd come out of the woodwork to help onlist, but I'm
rarely engaged with Forrest as a code base anymore so I'm unlikely to
create the page/address the issue directly.

If we add a tag to the description, or something like that, then we
could create a standard search and automatically generate the page.

Ross

David Crossley (JIRA) wrote:

> [ https://issues.apache.org/jira/browse/FOR-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> David Crossley updated FOR-1005:
> --------------------------------
>
> Attachment: FOR-1005-sourcetype-plugins.txt
>
> The attached file FOR-1005-sourcetype-plugins.txt is a list of all current plugins. In column #1 is a symbol to indicate its status. So far i have just used 'find and grep' to see if their sitemaps use "sourcetype". There are 49 plugins, of which 11 use sourcetype.
>
>> Use sourcetypeaction for input plugins
>> --------------------------------------
>>
>> Key: FOR-1005
>> URL: https://issues.apache.org/jira/browse/FOR-1005
>> Project: Forrest
>> Issue Type: Improvement
>> Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
>> Affects Versions: 0.9-dev
>> Reporter: Ross Gardler
>> Attachments: FOR-1005-sourcetype-plugins.txt
>>
>>
>> Wherever possible input plugins should use the sourcetypeaction to figure out whether to process a file or not.
>> Too many plugins use a fixed url space for this, it is not maintainable.
>

[jira] Updated: (FOR-1005) Use sourcetypeaction for input plugins

2008-11-20T22:24:44Z

[ https://issues.apache.org/jira/browse/FOR-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-1005:
--------------------------------

Attachment: FOR-1005-sourcetype-plugins.txt

The attached file FOR-1005-sourcetype-plugins.txt is a list of all current plugins. In column #1 is a symbol to indicate its status. So far i have just used 'find and grep' to see if their sitemaps use "sourcetype". There are 49 plugins, of which 11 use sourcetype.

> Use sourcetypeaction for input plugins
> --------------------------------------
>
> Key: FOR-1005
> URL: https://issues.apache.org/jira/browse/FOR-1005
> Project: Forrest
> Issue Type: Improvement
> Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
> Affects Versions: 0.9-dev
> Reporter: Ross Gardler
> Attachments: FOR-1005-sourcetype-plugins.txt
>
>
> Wherever possible input plugins should use the sourcetypeaction to figure out whether to process a file or not.
> Too many plugins use a fixed url space for this, it is not maintainable.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (FOR-1005) Use sourcetypeaction for input plugins

2008-11-20T22:12:44Z

[ https://issues.apache.org/jira/browse/FOR-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649609#action_12649609 ]

David Crossley commented on FOR-1005:
-------------------------------------

Ross refers to our powerful "SourceTypeAction (content aware pipelines)"
http://forrest.apache.org/docs/dev/cap.html
This detects properties of the input sources and responds accordingly.

Two examples are org.apache.forrest.plugin.input.foaf which acts on "document-element namespace" and org.apache.forrest.plugin.input.simplifiedDocbook which acts on "document-declaration public-id". There are other methods, and more could be added.

If any Forrest developer would like to get involved with a task, then this would be a great contribution. A good way to get familiar with the internals of Forrest.

> Use sourcetypeaction for input plugins
> --------------------------------------
>
> Key: FOR-1005
> URL: https://issues.apache.org/jira/browse/FOR-1005
> Project: Forrest
> Issue Type: Improvement
> Components: Plugin: input.doap, Plugin: input.foaf, Plugin: input.skos
> Affects Versions: 0.9-dev
> Reporter: Ross Gardler
>
> Wherever possible input plugins should use the sourcetypeaction to figure out whether to process a file or not.
> Too many plugins use a fixed url space for this, it is not maintainable.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: FOR-1108 on Mac

2008-11-20T21:09:36Z

Tim Williams wrote:

> David Crossley wrote:
> > Tim Williams wrote:
> >> David Crossley wrote:
> >> > Tim Williams wrote:
> >> >> David Crossley wrote:
> >> >
> >> > What are the errors that you are seeing?
> >> >
> >> >> There is actually a note at the bottom of
> >> >> /samples-b/linking.html that gives a obscure clue - reading that note
> >> >> it's still not clear to me why it fails to harshly at this point.
> >> >
> >> > That note is attempting to explain that the generated
> >> > docs (as deployed on the zone) are not at the root of
> >> > the webserver, hence the generated paths for some of
> >> > the image references are not showing correctly.
> >> > I don't understand how that would relate to FOR-1108.
> >>
> >> Ok, apologies in advance if I'm missing something incredibly obvious -
> >> I'm coming from a long hibernation...
> >>
> >> So, I'm failing with a NPE just like the attached log file in
> >> FOR-1108.
> >
> > That is not related to FOR-1108. It is something else
> > that appeared around the same time. It came along with
> > the upgrade of our PDF output plugin. See the dev archives,
> > where there is some discussion about it between me and Jeremias.
>
> This is bizarre. It was a discussion between you a Jeremias[1] that
> led me to FOR-1108 because of Ross' concluding mail[2].

That [1] is not the conversation that i was referring to.
This is it a little further in that thread:
[3] http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c20080912114226.GD2534@...%3e

There are two separate issues:

*) The one with icon-b and the NPE. See [3] and see
the first part of the output listing in [1].

*) The crux of FOR-1108, which is the part where
it fails (only on Windows we thought) with the very
corrupted path to dataModel.xmap file. See the
the seconds part of the output listing in [1].

-----------
X [0] linkmap.html BROKEN: C:\Dev\apache.org\rw\forrest-trunk\main\webapp\.\C:\Dev\apache.org\rw\forrest-trunk\build\test_d
ispatcher_site\build\tmp\C:\Dev\apache.org\rw\forrest-trunk\build\plugins\dataModel.xmap
-----------

So are you seeing a similarly corrupted path too?

-David

> My stacktrace
> looks nearly identical to theirs. So, they may not have exactly the
> same cause, I find it difficult to believe they'd produce such an
> identical stacktrace, bomb at the exact same spot, and not, somehow,
> be related. I did -some- homework prior to my first mail...
>
> --tim
>
> [1] - http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c20080912094922.ADEA.60BA733C@...%3e
> [2] - http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c48CAD2D7.9070405@...%3e

[jira] Commented: (FOR-984) validate-sitemap target fails relaxng validation on some JDK 1.6: missing datatypes

2008-11-20T20:24:44Z

[ https://issues.apache.org/jira/browse/FOR-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649593#action_12649593 ]

David Crossley commented on FOR-984:
------------------------------------

Would someone on Java 6 please test the current Forrest trunk SVN.

]$ cd my-new-dir
]$ forrest seed
]$ forrest validate

It should now get past the "validate-sitemap" stage.

> validate-sitemap target fails relaxng validation on some JDK 1.6: missing datatypes
> -----------------------------------------------------------------------------------
>
> Key: FOR-984
> URL: https://issues.apache.org/jira/browse/FOR-984
> Project: Forrest
> Issue Type: Improvement
> Components: Core operations, Launch 'forrest'
> Affects Versions: 0.8, 0.9-dev
> Reporter: Schumarer
> Fix For: 0.9-dev
>
> Attachments: log.txt
>
>
> Doing 'forrest' fails at the validate-sitemap task. Missing the RELAX NG datatype library ...
> validate-sitemap:
> D:\apache-forrest-0.8rc\main\webapp\resources\schema\relaxng\sitemap-v06.rng:72:31:
> error: datatype library "http://www.w3.org/2001/XMLSchema-datatypes" not recognized
> People should be able to work around that by editing their forrest.properties configuration to expose the "forrest.validate.sitemap" property and set it to "false". Might need to do the same for the "forrest.validate.stylesheets" property.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: FOR-1108 on Mac

2008-11-20T20:16:13Z

On Thu, Nov 20, 2008 at 11:02 PM, David Crossley <crossley@...> wrote:

> Tim Williams wrote:
>> David Crossley wrote:
>> > Tim Williams wrote:
>> >> David Crossley wrote:
>> >
>> > What are the errors that you are seeing?
>> >
>> >> There is actually a note at the bottom of
>> >> /samples-b/linking.html that gives a obscure clue - reading that note
>> >> it's still not clear to me why it fails to harshly at this point.
>> >
>> > That note is attempting to explain that the generated
>> > docs (as deployed on the zone) are not at the root of
>> > the webserver, hence the generated paths for some of
>> > the image references are not showing correctly.
>> > I don't understand how that would relate to FOR-1108.
>>
>> Ok, apologies in advance if I'm missing something incredibly obvious -
>> I'm coming from a long hibernation...
>>
>> So, I'm failing with a NPE just like the attached log file in
>> FOR-1108.
>
> That is not related to FOR-1108. It is something else
> that appeared around the same time. It came along with
> the upgrade of our PDF output plugin. See the dev archives,
> where there is some discussion about it between me and Jeremias.

This is bizarre. It was a discussion between you a Jeremias[1] that
led me to FOR-1108 because of Ross' concluding mail[2]. My stacktrace
looks nearly identical to theirs. So, they may not have exactly the
same cause, I find it difficult to believe they'd produce such an
identical stacktrace, bomb at the exact same spot, and not, somehow,
be related. I did -some- homework prior to my first mail...

--tim

[1] - http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c20080912094922.ADEA.60BA733C@...%3e
[2] - http://mail-archives.apache.org/mod_mbox/forrest-dev/200809.mbox/%3c48CAD2D7.9070405@...%3e

Re: FOR-1108 on Mac

2008-11-20T20:02:21Z

Tim Williams wrote:

> David Crossley wrote:
> > Tim Williams wrote:
> >> David Crossley wrote:
> >
> > What are the errors that you are seeing?
> >
> >> There is actually a note at the bottom of
> >> /samples-b/linking.html that gives a obscure clue - reading that note
> >> it's still not clear to me why it fails to harshly at this point.
> >
> > That note is attempting to explain that the generated
> > docs (as deployed on the zone) are not at the root of
> > the webserver, hence the generated paths for some of
> > the image references are not showing correctly.
> > I don't understand how that would relate to FOR-1108.
>
> Ok, apologies in advance if I'm missing something incredibly obvious -
> I'm coming from a long hibernation...
>
> So, I'm failing with a NPE just like the attached log file in
> FOR-1108.

That is not related to FOR-1108. It is something else
that appeared around the same time. It came along with
the upgrade of our PDF output plugin. See the dev archives,
where there is some discussion about it between me and Jeremias.

-David

> Looking into this led me to linking.html. Specifically,
> these output lines:
>
> * [88/12] [12/50] 0.155s 30.3Kb samples-b/linking.html
> * [97/3] [0/0] 0.09s 1.9Kb /images/ellipse-2.png
> ERROR - Image not found: cocoon:/images/icon-b.png
> ERROR - Image not found: cocoon:/images/icon-b.png
> java.lang.NullPointerException
> at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
> at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
> at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)
>
>
> So, I think, icon-b.png - let me investigate that a bit. I notice the
> comments and they don't immediately make sense. Then I look at my
> file system and, sure enough, forrest has placed icon-b.png in an
> images directory that is sibling to the site build directory. This is
> why I think they're related. Then... I finally read the comments on
> the reference to 'icon-b.png':
>
> "Broken relative reference (it points up beyond the document root).
> Never mind, Forrest "absolutizes" the URLs to be like the URLs in
> examples 1 and 2 and 3. The source file is found in
> src/documentation/resources/images/ directory. However there is a
> problem here. When using Forrest in command-line mode, the image will
> be generated outside the document directory. It is better to use
> absolute /image/ URLs or be very careful about using such relative
> links (Forrest will not report an error)."
>
> It's starting to make a little more sense, but while I'm trying to
> figure out what is exactly breaking, I keeping wondering why in the
> heck we want to even to try overcome a site admin being a complete
> moron in the first place? Throwing an NPE is bad, but I'm thinking
> trying to be this helpful in the first place is also bad. But then
> again, I've been away for quite some time, so this could eventually
> turn out to be a user error :<\
>
> --tim

Re: FOR-1108 on Mac

2008-11-20T19:51:08Z

On Thu, Nov 20, 2008 at 10:39 PM, David Crossley <crossley@...> wrote:

> Tim Williams wrote:
>> David Crossley wrote:
>> > Tim Williams wrote:
>> >> Hey Devs-
>> >> I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to
>> >> date but that would mean trunk has been broken for quite some time, so
>> >> I thought I'd just ask before looking into it. It seems to have been
>> >> reported only relative to a platform (windows) so I thought it weird
>> >> to be seeing it too. Is the trunk still broken?
>> >>
>> >> https://issues.apache.org/jira/browse/FOR-1108
>> >
>> > As far as i remember, you are the first to report a
>> > problem on a modern Mac.
>> >
>> > Now searching the archives i found this from Sjur:
>> > http://marc.info/?l=forrest-dev&m=122112679627853
>> > "Re: [STATUS] [heads-up] merging our branch Cocoon-2.1"
>> > which indicates that it was okay on Leopard.
>> >
>> > Perhaps you can help to debug it, as it seems that
>> > our Windows developers have not yet found time.
>> > Cyriaque added a new observation recently to FOR-1108.
>> >
>> > Trunk works fine for me on this older Mac OSX Tiger.
>> > And it is fine on Solaris 10, as the forrestbot on the
>> > Forrest zones server is okay. Also fine for Thorsten
>> > and Brian on Linux.
>>
>> Actually, according to that mail, Sjur was only able to test in "run"
>> mode which does indeed work for me too - the problem occurs in forrest
>> site.
>
> What are the errors that you are seeing?
>
>> There is actually a note at the bottom of
>> /samples-b/linking.html that gives a obscure clue - reading that note
>> it's still not clear to me why it fails to harshly at this point.
>
> That note is attempting to explain that the generated
> docs (as deployed on the zone) are not at the root of
> the webserver, hence the generated paths for some of
> the image references are not showing correctly.
> I don't understand how that would relate to FOR-1108.

Ok, apologies in advance if I'm missing something incredibly obvious -
I'm coming from a long hibernation...

So, I'm failing with a NPE just like the attached log file in
FOR-1108. Looking into this led me to linking.html. Specifically,
these output lines:

* [88/12] [12/50] 0.155s 30.3Kb samples-b/linking.html
* [97/3] [0/0] 0.09s 1.9Kb /images/ellipse-2.png
ERROR - Image not found: cocoon:/images/icon-b.png
ERROR - Image not found: cocoon:/images/icon-b.png
java.lang.NullPointerException
at org.apache.cocoon.environment.AbstractEnvironment.release(AbstractEnvironment.java:563)
at org.apache.cocoon.environment.wrapper.MutableEnvironmentFacade.release(MutableEnvironmentFacade.java:314)
at org.apache.cocoon.generation.FileGenerator.recycle(FileGenerator.java:64)

So, I think, icon-b.png - let me investigate that a bit. I notice the
comments and they don't immediately make sense. Then I look at my
file system and, sure enough, forrest has placed icon-b.png in an
images directory that is sibling to the site build directory. This is
why I think they're related. Then... I finally read the comments on
the reference to 'icon-b.png':

"Broken relative reference (it points up beyond the document root).
Never mind, Forrest "absolutizes" the URLs to be like the URLs in
examples 1 and 2 and 3. The source file is found in
src/documentation/resources/images/ directory. However there is a
problem here. When using Forrest in command-line mode, the image will
be generated outside the document directory. It is better to use
absolute /image/ URLs or be very careful about using such relative
links (Forrest will not report an error)."

It's starting to make a little more sense, but while I'm trying to
figure out what is exactly breaking, I keeping wondering why in the
heck we want to even to try overcome a site admin being a complete
moron in the first place? Throwing an NPE is bad, but I'm thinking
trying to be this helpful in the first place is also bad. But then
again, I've been away for quite some time, so this could eventually
turn out to be a user error :<\

--tim

Re: FOR-1108 on Mac

2008-11-20T19:39:00Z

Tim Williams wrote:

> David Crossley wrote:
> > Tim Williams wrote:
> >> Hey Devs-
> >> I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to
> >> date but that would mean trunk has been broken for quite some time, so
> >> I thought I'd just ask before looking into it. It seems to have been
> >> reported only relative to a platform (windows) so I thought it weird
> >> to be seeing it too. Is the trunk still broken?
> >>
> >> https://issues.apache.org/jira/browse/FOR-1108
> >
> > As far as i remember, you are the first to report a
> > problem on a modern Mac.
> >
> > Now searching the archives i found this from Sjur:
> > http://marc.info/?l=forrest-dev&m=122112679627853
> > "Re: [STATUS] [heads-up] merging our branch Cocoon-2.1"
> > which indicates that it was okay on Leopard.
> >
> > Perhaps you can help to debug it, as it seems that
> > our Windows developers have not yet found time.
> > Cyriaque added a new observation recently to FOR-1108.
> >
> > Trunk works fine for me on this older Mac OSX Tiger.
> > And it is fine on Solaris 10, as the forrestbot on the
> > Forrest zones server is okay. Also fine for Thorsten
> > and Brian on Linux.
>
> Actually, according to that mail, Sjur was only able to test in "run"
> mode which does indeed work for me too - the problem occurs in forrest
> site.

What are the errors that you are seeing?

> There is actually a note at the bottom of
> /samples-b/linking.html that gives a obscure clue - reading that note
> it's still not clear to me why it fails to harshly at this point.

That note is attempting to explain that the generated
docs (as deployed on the zone) are not at the root of
the webserver, hence the generated paths for some of
the image references are not showing correctly.
I don't understand how that would relate to FOR-1108.

-David

Re: FOR-1108 on Mac

2008-11-20T19:24:12Z

On Thu, Nov 20, 2008 at 9:58 PM, David Crossley <crossley@...> wrote:

> Tim Williams wrote:
>> Hey Devs-
>> I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to
>> date but that would mean trunk has been broken for quite some time, so
>> I thought I'd just ask before looking into it. It seems to have been
>> reported only relative to a platform (windows) so I thought it weird
>> to be seeing it too. Is the trunk still broken?
>>
>> https://issues.apache.org/jira/browse/FOR-1108
>
> As far as i remember, you are the first to report a
> problem on a modern Mac.
>
> Now searching the archives i found this from Sjur:
> http://marc.info/?l=forrest-dev&m=122112679627853
> "Re: [STATUS] [heads-up] merging our branch Cocoon-2.1"
> which indicates that it was okay on Leopard.
>
> Perhaps you can help to debug it, as it seems that
> our Windows developers have not yet found time.
> Cyriaque added a new observation recently to FOR-1108.
>
> Trunk works fine for me on this older Mac OSX Tiger.
> And it is fine on Solaris 10, as the forrestbot on the
> Forrest zones server is okay. Also fine for Thorsten
> and Brian on Linux.

Actually, according to that mail, Sjur was only able to test in "run"
mode which does indeed work for me too - the problem occurs in forrest
site. There is actually a note at the bottom of
/samples-b/linking.html that gives a obscure clue - reading that note
it's still not clear to me why it fails to harshly at this point.

--tim

Re: FOR-1108 on Mac

2008-11-20T18:58:06Z

Tim Williams wrote:
> Hey Devs-
> I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to
> date but that would mean trunk has been broken for quite some time, so
> I thought I'd just ask before looking into it. It seems to have been
> reported only relative to a platform (windows) so I thought it weird
> to be seeing it too. Is the trunk still broken?
>
> https://issues.apache.org/jira/browse/FOR-1108

As far as i remember, you are the first to report a
problem on a modern Mac.

Now searching the archives i found this from Sjur:
http://marc.info/?l=forrest-dev&m=122112679627853
"Re: [STATUS] [heads-up] merging our branch Cocoon-2.1"
which indicates that it was okay on Leopard.

Perhaps you can help to debug it, as it seems that
our Windows developers have not yet found time.
Cyriaque added a new observation recently to FOR-1108.

Trunk works fine for me on this older Mac OSX Tiger.
And it is fine on Solaris 10, as the forrestbot on the
Forrest zones server is okay. Also fine for Thorsten
and Brian on Linux.

-David

FOR-1108 on Mac

2008-11-20T18:01:51Z

Hey Devs-
I'm seeing FOR-1108 on OSX Leopard. I would assume that JIRA is up to
date but that would mean trunk has been broken for quite some time, so
I thought I'd just ask before looking into it. It seems to have been
reported only relative to a platform (windows) so I thought it weird
to be seeing it too. Is the trunk still broken?

https://issues.apache.org/jira/browse/FOR-1108

Thanks,
--tim

[jira] Updated: (FOR-1129) Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'

2008-11-20T17:00:46Z

[ https://issues.apache.org/jira/browse/FOR-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Crossley updated FOR-1129:
--------------------------------

Description:
I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' operations using the java 1.5.0_12 jre. I expectrd a default site to be created, but got the following error. After posting to the forrest mail group, it was recommended that i raise an issue.

was:
I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' operations using the java 1.5.0_12 jre. I expectrd a default site to be created, but got the following error. After posting to the forrest mail group, it was recommended that i raise an issue.

Regards,

-------------------------------------

Seed operation

Apache Forrest. Run 'forrest -projecthelp' to list options

Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml

seed:
Copying 80 files to C:\projects\Libs\apache-forrest-0.8\sites\java5
Copied 18 empty directories to 2 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5

-------------------------------
~~ Template project created! ~~

Here is an outline of the generated files:

/ # C:\projects\Libs\apache-forrest-0.8\sites\java5
/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/xdocs/*.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.
- 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@...

Thanks for using Apache Forrest
-------------------------------

BUILD SUCCESSFUL
Total time: 2 seconds

Apache Forrest. Run 'forrest -projecthelp' to list options

Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml

check-java-version:
This is apache-forrest-0.8
Using Java 1.5 from p:\javasoft\jdk\1.5.0_12\jre

fetch-plugins-descriptors:
Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
local file date : Sun Apr 15 13:42:28 BST 2007
Error getting http://forrest.apache.org/plugins/plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml
Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
local file date : Sun Apr 15 13:42:28 BST 2007
Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

--------------------------------------------------------------
Installing plugin: org.apache.forrest.plugin.output.pdf
--------------------------------------------------------------

check-plugin:
org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update it...

fetch-plugin:
Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files
Using the descriptor file C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml...
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\pluginlist2fetchbuild.xml
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginlist2fetch.xsl

get-local:
Trying to locally get org.apache.forrest.plugin.output.pdf
Looking in local C:\projects\Libs\apache-forrest-0.8/plugins
Found !

local-deploy:
Locally deploying org.apache.forrest.plugin.output.pdf
Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure
Fetch-plugin Ok, installing !

configure-output-plugin:
Mounting output plugin: org.apache.forrest.plugin.output.pdf
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap.new
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginMountSnippet.xsl
Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

configure-plugin-locationmap:
Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml.new
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginLmMountSnippet.xsl
Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

validate-xdocs:
...validated xdocs

validate-skinconf:
1 file(s) have been successfully validated.
...validated skinconf

validate-sitemap:
...validated project sitemap

validate-skinchoice:
...validated existence of skin 'pelt'

site:

Copying the various non-generated resources to site.
Warnings will be issued if the optional project resources are not found.
This is often the case, because they are optional and so may not be available.
Copying project resources and images to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\webapp\resources not found.
Copying 2 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en
Copying main skin images to site ...
Created dir: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying 18 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying 14 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying project skin images to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common\images not found.
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt\images not found.
Copying main skin css and js files to site ...
Copying 11 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copied 4 empty directories to 3 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copying 4 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copying project skin css and js files to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common not found.
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt not found.

Finished copying the non-generated resources.
Now Cocoon will generate the rest.

Static site will be generated at:
C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en

Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).

------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2005 Apache Software Foundation. All rights reserved.
Build: December 8 2005 (TargetVM=1.4, SourceVM=1.4, Debug=on, Optimize=on)
------------------------------------------------------------------------
* [1/0] [0/0] 0.406s 0b linkmap.html
org.apache.cocoon.sitemap.PatternException: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:250)
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(PreparedVariableResolver.java:197)
at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:77)
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:155)
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:95)
at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:292)
at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:223)
at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:289)
at org.apache.cocoon.Cocoon.process(Cocoon.java:557)
at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:426)
at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:496)
at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:357)
at org.apache.cocoon.Main.main(Main.java:311)
Caused by: org.apache.avalon.framework.configuration.ConfigurationException: Unable to build LocationMap.
at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:148)
at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:105)
at org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapModule.java:203)
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:246)
... 14 more
Caused by: org.apache.excalibur.source.SourceException: Cannot get input stream for cocoon://locationmap.xml
at org.apache.cocoon.components.source.impl.SitemapSource.getInputStream(SitemapSource.java:184)
at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:144)
... 17 more
Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found.
at <map:mount> - file:/C:/projects/Libs/apache-forrest-0.8/main/webapp/./sitemap.xmap:402:72
at org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:313)
at org.apache.cocoon.components.source.impl.SitemapSource.<init>(SitemapSource.java:146)
at org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:65)
at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:159)
at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:189)
at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:95)
... 16 more
X [0] linkmap.html BROKEN: URI not found: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
Total time: 0 minutes 4 seconds, Site size: 0 Site pages: 1
Java Result: 1

Copying broken links file to site root.

Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en

BUILD FAILED
C:\projects\Libs\apache-forrest-0.8\main\targets\site.xml:180: Error building site.

There appears to be a problem with your site build.

Read the output above:
* Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
* Even if only one link is broken, you will still get "failed".
* Your site would still be generated, but some pages would be broken.
- See C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en/broken-links.xml

Total time: 50 seconds

Removed output text from issue description. See the attached files.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Forrest friendly searching

2008-11-20T05:03:04Z

Tim Williams wrote:

> I've been playing around with Google's Custom Search and thought I'd
> use Forrest as my playground since I have a good idea of what I think
> "good" results are. Anyway, I haven't added a whole lot of
> customization or refinements to it but think it's already fairly
> useful nonetheless.
>
>
> http://www.google.com/coop/cse?cx=014207783617196158741:fgpzn29ywzq
>
>
> e.g.
> http://www.google.com/cse?cx=014207783617196158741%3Afgpzn29ywzq&q=dispatcher
>
>
> Let me know what you think and let me know if you want to contribute...
>
> btw, i just picked a reasonable name, if it violates some rule, let me know...

Quite the contrary. As long as you are prepared to give committers who
ask for it the ability to work on the resources then I'd propose that
this become the default search facility on our site.

Ross

[jira] Updated: (FOR-1129) Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'

2008-11-20T03:56:46Z

[ https://issues.apache.org/jira/browse/FOR-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul O'Connell updated FOR-1129:
--------------------------------

Attachment: site.txt
seed.txt

The seed and site logs

> Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
> --------------------------------------------------------------------------------
>
> Key: FOR-1129
> URL: https://issues.apache.org/jira/browse/FOR-1129
> Project: Forrest
> Issue Type: Bug
> Components: Core operations
> Affects Versions: 0.8
> Reporter: Paul O'Connell
> Attachments: seed.txt, site.txt
>
>
> I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' operations using the java 1.5.0_12 jre. I expectrd a default site to be created, but got the following error. After posting to the forrest mail group, it was recommended that i raise an issue.
> Regards,
> -------------------------------------
> Seed operation
> Apache Forrest. Run 'forrest -projecthelp' to list options
> Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml
> seed:
> Copying 80 files to C:\projects\Libs\apache-forrest-0.8\sites\java5
> Copied 18 empty directories to 2 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5
> -------------------------------
> ~~ Template project created! ~~
> Here is an outline of the generated files:
> / # C:\projects\Libs\apache-forrest-0.8\sites\java5
> /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/xdocs/*.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.
> - 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@...
> Thanks for using Apache Forrest
> -------------------------------
> BUILD SUCCESSFUL
> Total time: 2 seconds
> Apache Forrest. Run 'forrest -projecthelp' to list options
> Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml
> check-java-version:
> This is apache-forrest-0.8
> Using Java 1.5 from p:\javasoft\jdk\1.5.0_12\jre
> fetch-plugins-descriptors:
> Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml
> Getting: http://forrest.apache.org/plugins/plugins.xml
> To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
> local file date : Sun Apr 15 13:42:28 BST 2007
> Error getting http://forrest.apache.org/plugins/plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
> Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml
> Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
> To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
> local file date : Sun Apr 15 13:42:28 BST 2007
> Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
> Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
> Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml.
> init-plugins:
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> --------------------------------------------------------------
> Installing plugin: org.apache.forrest.plugin.output.pdf
> --------------------------------------------------------------
>
> check-plugin:
> org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update it...
> fetch-plugin:
> Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files
> Using the descriptor file C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml...
> Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\pluginlist2fetchbuild.xml
> Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginlist2fetch.xsl
> get-local:
> Trying to locally get org.apache.forrest.plugin.output.pdf
> Looking in local C:\projects\Libs\apache-forrest-0.8/plugins
> Found !
> local-deploy:
> Locally deploying org.apache.forrest.plugin.output.pdf
> Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure
> Fetch-plugin Ok, installing !
> configure-output-plugin:
> Mounting output plugin: org.apache.forrest.plugin.output.pdf
> Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap.new
> Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginMountSnippet.xsl
> Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> configure-plugin-locationmap:
> Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
> Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml.new
> Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginLmMountSnippet.xsl
> Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
> validate-xdocs:
> ...validated xdocs
> validate-skinconf:
> 1 file(s) have been successfully validated.
> ...validated skinconf
> validate-sitemap:
> ...validated project sitemap
> validate-skinchoice:
> ...validated existence of skin 'pelt'
> site:
> Copying the various non-generated resources to site.
> Warnings will be issued if the optional project resources are not found.
> This is often the case, because they are optional and so may not be available.
> Copying project resources and images to site ...
> Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\webapp\resources not found.
> Copying 2 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en
> Copying main skin images to site ...
> Created dir: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
> Copying 18 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
> Copying 14 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
> Copying project skin images to site ...
> Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common\images not found.
> Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt\images not found.
> Copying main skin css and js files to site ...
> Copying 11 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
> Copied 4 empty directories to 3 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
> Copying 4 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
> Copying project skin css and js files to site ...
> Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common not found.
> Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt not found.
> Finished copying the non-generated resources.
> Now Cocoon will generate the rest.
> Static site will be generated at:
> C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en
> Cocoon will report the status of each document:
> - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
>
> ------------------------------------------------------------------------
> cocoon 2.2.0-dev
> Copyright (c) 1999-2005 Apache Software Foundation. All rights reserved.
> Build: December 8 2005 (TargetVM=1.4, SourceVM=1.4, Debug=on, Optimize=on)
> ------------------------------------------------------------------------
> * [1/0] [0/0] 0.406s 0b linkmap.html
> org.apache.cocoon.sitemap.PatternException: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
> at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:250)
> at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(PreparedVariableResolver.java:197)
> at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:77)
> at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
> at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:155)
> at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
> at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:95)
> at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:292)
> at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:223)
> at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:289)
> at org.apache.cocoon.Cocoon.process(Cocoon.java:557)
> at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:426)
> at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:496)
> at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:357)
> at org.apache.cocoon.Main.main(Main.java:311)
> Caused by: org.apache.avalon.framework.configuration.ConfigurationException: Unable to build LocationMap.
> at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:148)
> at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:105)
> at org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapModule.java:203)
> at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:246)
> ... 14 more
> Caused by: org.apache.excalibur.source.SourceException: Cannot get input stream for cocoon://locationmap.xml
> at org.apache.cocoon.components.source.impl.SitemapSource.getInputStream(SitemapSource.java:184)
> at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:144)
> ... 17 more
> Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found.
> at <map:mount> - file:/C:/projects/Libs/apache-forrest-0.8/main/webapp/./sitemap.xmap:402:72
> at org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:313)
> at org.apache.cocoon.components.source.impl.SitemapSource.<init>(SitemapSource.java:146)
> at org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:65)
> at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:159)
> at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:189)
> at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:95)
> ... 16 more
> X [0] linkmap.html BROKEN: URI not found: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
> Total time: 0 minutes 4 seconds, Site size: 0 Site pages: 1
> Java Result: 1
> Copying broken links file to site root.
>
> Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en
> BUILD FAILED
> C:\projects\Libs\apache-forrest-0.8\main\targets\site.xml:180: Error building site.
>
> There appears to be a problem with your site build.
> Read the output above:
> * Cocoon will report the status of each document:
> - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
> * Even if only one link is broken, you will still get "failed".
> * Your site would still be generated, but some pages would be broken.
> - See C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en/broken-links.xml
> Total time: 50 seconds

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (FOR-1129) Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'

2008-11-20T03:54:44Z

Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
--------------------------------------------------------------------------------

Key: FOR-1129
URL: https://issues.apache.org/jira/browse/FOR-1129
Project: Forrest
Issue Type: Bug
Components: Core operations
Affects Versions: 0.8
Reporter: Paul O'Connell

I extracted forrest 0.8 on windows xp, and ran the 'site' and 'seed' operations using the java 1.5.0_12 jre. I expectrd a default site to be created, but got the following error. After posting to the forrest mail group, it was recommended that i raise an issue.

Regards,

-------------------------------------

Seed operation

Apache Forrest. Run 'forrest -projecthelp' to list options

Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml

seed:
Copying 80 files to C:\projects\Libs\apache-forrest-0.8\sites\java5
Copied 18 empty directories to 2 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5

-------------------------------
~~ Template project created! ~~

Here is an outline of the generated files:

/ # C:\projects\Libs\apache-forrest-0.8\sites\java5
/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/xdocs/*.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.
- 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@...

Thanks for using Apache Forrest
-------------------------------

BUILD SUCCESSFUL
Total time: 2 seconds

Apache Forrest. Run 'forrest -projecthelp' to list options

Buildfile: C:\projects\Libs\apache-forrest-0.8\bin\..\main\forrest.build.xml

check-java-version:
This is apache-forrest-0.8
Using Java 1.5 from p:\javasoft\jdk\1.5.0_12\jre

fetch-plugins-descriptors:
Fetching plugins descriptor: http://forrest.apache.org/plugins/plugins.xml
Getting: http://forrest.apache.org/plugins/plugins.xml
To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
local file date : Sun Apr 15 13:42:28 BST 2007
Error getting http://forrest.apache.org/plugins/plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml
Fetching plugins descriptor: http://forrest.apache.org/plugins/whiteboard-plugins.xml
Getting: http://forrest.apache.org/plugins/whiteboard-plugins.xml
To: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
local file date : Sun Apr 15 13:42:28 BST 2007
Error getting http://forrest.apache.org/plugins/whiteboard-plugins.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-2.xml
Plugin list loaded from http://forrest.apache.org/plugins/plugins.xml.
Plugin list loaded from http://forrest.apache.org/plugins/whiteboard-plugins.xml.

init-plugins:
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp
Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

--------------------------------------------------------------
Installing plugin: org.apache.forrest.plugin.output.pdf
--------------------------------------------------------------

check-plugin:
org.apache.forrest.plugin.output.pdf is available in the build dir. Trying to update it...

fetch-plugin:
Trying to find the description of org.apache.forrest.plugin.output.pdf in the different descriptor files
Using the descriptor file C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml...
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\plugins-1.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\pluginlist2fetchbuild.xml
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginlist2fetch.xsl

get-local:
Trying to locally get org.apache.forrest.plugin.output.pdf
Looking in local C:\projects\Libs\apache-forrest-0.8/plugins
Found !

local-deploy:
Locally deploying org.apache.forrest.plugin.output.pdf
Plugin org.apache.forrest.plugin.output.pdf deployed ! Ready to configure
Fetch-plugin Ok, installing !

configure-output-plugin:
Mounting output plugin: org.apache.forrest.plugin.output.pdf
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\output.xmap.new
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginMountSnippet.xsl
Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

configure-plugin-locationmap:
Mounting plugin locationmap for org.apache.forrest.plugin.output.pdf
Processing C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp\locationmap.xml.new
Loading stylesheet C:\projects\Libs\apache-forrest-0.8\main\var\pluginLmMountSnippet.xsl
Moving 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\tmp

validate-xdocs:
...validated xdocs

validate-skinconf:
1 file(s) have been successfully validated.
...validated skinconf

validate-sitemap:
...validated project sitemap

validate-skinchoice:
...validated existence of skin 'pelt'

site:

Copying the various non-generated resources to site.
Warnings will be issued if the optional project resources are not found.
This is often the case, because they are optional and so may not be available.
Copying project resources and images to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\webapp\resources not found.
Copying 2 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en
Copying main skin images to site ...
Created dir: C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying 18 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying 14 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin\images
Copying project skin images to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common\images not found.
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt\images not found.
Copying main skin css and js files to site ...
Copying 11 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copied 4 empty directories to 3 empty directories under C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copying 4 files to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en\skin
Copying project skin css and js files to site ...
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\common not found.
Warning: C:\projects\Libs\apache-forrest-0.8\sites\java5\src\documentation\skins\pelt not found.

Finished copying the non-generated resources.
Now Cocoon will generate the rest.

Static site will be generated at:
C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en

Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).

------------------------------------------------------------------------
cocoon 2.2.0-dev
Copyright (c) 1999-2005 Apache Software Foundation. All rights reserved.
Build: December 8 2005 (TargetVM=1.4, SourceVM=1.4, Debug=on, Optimize=on)
------------------------------------------------------------------------
* [1/0] [0/0] 0.406s 0b linkmap.html
org.apache.cocoon.sitemap.PatternException: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:250)
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.resolve(PreparedVariableResolver.java:197)
at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:77)
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:155)
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:77)
at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:95)
at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:292)
at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:223)
at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:289)
at org.apache.cocoon.Cocoon.process(Cocoon.java:557)
at org.apache.cocoon.bean.CocoonWrapper.getPage(CocoonWrapper.java:426)
at org.apache.cocoon.bean.CocoonBean.processTarget(CocoonBean.java:496)
at org.apache.cocoon.bean.CocoonBean.process(CocoonBean.java:357)
at org.apache.cocoon.Main.main(Main.java:311)
Caused by: org.apache.avalon.framework.configuration.ConfigurationException: Unable to build LocationMap.
at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:148)
at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:105)
at org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapModule.java:203)
at org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolver.processModule(PreparedVariableResolver.java:246)
... 14 more
Caused by: org.apache.excalibur.source.SourceException: Cannot get input stream for cocoon://locationmap.xml
at org.apache.cocoon.components.source.impl.SitemapSource.getInputStream(SitemapSource.java:184)
at org.apache.forrest.locationmap.LocationMapModule.loadConfiguration(LocationMapModule.java:144)
... 17 more
Caused by: org.apache.cocoon.ResourceNotFoundException: Resource not found.
at <map:mount> - file:/C:/projects/Libs/apache-forrest-0.8/main/webapp/./sitemap.xmap:402:72
at org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:313)
at org.apache.cocoon.components.source.impl.SitemapSource.<init>(SitemapSource.java:146)
at org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:65)
at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:159)
at org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:189)
at org.apache.forrest.locationmap.LocationMapModule.getLocationMap(LocationMapModule.java:95)
... 16 more
X [0] linkmap.html BROKEN: URI not found: Cannot get variable 'plugin.xmap.output' in expression '{lm:plugin.xmap.output}'
Total time: 0 minutes 4 seconds, Site size: 0 Site pages: 1
Java Result: 1

Copying broken links file to site root.

Copying 1 file to C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en

BUILD FAILED
C:\projects\Libs\apache-forrest-0.8\main\targets\site.xml:180: Error building site.

There appears to be a problem with your site build.

Read the output above:
* Cocoon will report the status of each document:
- in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
* Even if only one link is broken, you will still get "failed".
* Your site would still be generated, but some pages would be broken.
- See C:\projects\Libs\apache-forrest-0.8\sites\java5\build\site\en/broken-links.xml

Total time: 50 seconds

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Forrest friendly searching

2008-11-19T18:06:39Z

I've been playing around with Google's Custom Search and thought I'd
use Forrest as my playground since I have a good idea of what I think
"good" results are. Anyway, I haven't added a whole lot of
customization or refinements to it but think it's already fairly
useful nonetheless.

http://www.google.com/coop/cse?cx=014207783617196158741:fgpzn29ywzq

e.g.
http://www.google.com/cse?cx=014207783617196158741%3Afgpzn29ywzq&q=dispatcher

Let me know what you think and let me know if you want to contribute...

btw, i just picked a reasonable name, if it violates some rule, let me know...

--tim

[jira] Subscription: FOR-open-with-patch

2008-11-16T12:30:46Z

Issue Subscription
Filter: FOR-open-with-patch (12 issues)
Subscriber: rgardler

Key Summary
FOR-211 whole-site html and pdf: broken ext links
https://issues.apache.org/jira/browse/FOR-211
FOR-969 Add sensible site navigation in DOAP plugin
https://issues.apache.org/jira/browse/FOR-969
FOR-355 Improved PDF configurability (e.g., TOC, Page Numbers, logo)
https://issues.apache.org/jira/browse/FOR-355
FOR-652 CSS Style Sheets need cleanup, optimization and better naming of elements
https://issues.apache.org/jira/browse/FOR-652
FOR-998 [PATCH] Resolve empty cells.
https://issues.apache.org/jira/browse/FOR-998
FOR-707 Document i18n features of Forrest
https://issues.apache.org/jira/browse/FOR-707
FOR-412 use CSS for displaying list of Changes
https://issues.apache.org/jira/browse/FOR-412
FOR-311 OOo Headings bug causes Forrest to fail
https://issues.apache.org/jira/browse/FOR-311
FOR-934 i18n language override menu
https://issues.apache.org/jira/browse/FOR-934
FOR-280 gather index terms from documents to create index page with links
https://issues.apache.org/jira/browse/FOR-280
FOR-752 Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory
https://issues.apache.org/jira/browse/FOR-752
FOR-795 Navigation bars for easy access in long documents
https://issues.apache.org/jira/browse/FOR-795

[jira] Commented: (FOR-1055) forrest.echo propery is always true if not commented out

2008-11-13T18:02:44Z

[ https://issues.apache.org/jira/browse/FOR-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647499#action_12647499 ]

Gavin commented on FOR-1055:
----------------------------

Yeah, it's being handled differently, the forrest.echo is is being detected for its presence by 'if' (opposite reaction of 'unless' )

So we would have to refactor it a bit to behave like other properties, not sure how much work that is , I'll check later.

> forrest.echo propery is always true if not commented out
> --------------------------------------------------------
>
> Key: FOR-1055
> URL: https://issues.apache.org/jira/browse/FOR-1055
> Project: Forrest
> Issue Type: Bug
> Components: Other
> Reporter: Michael Parker
> Assignee: Gavin
> Priority: Trivial
>
> The propertty forrest.echo causes an echo of the settings only by its existence not by the value.
> Example
> # Prints out a summary of Forrest settings for this project
> forrest.echo=false
> will lead to a print out.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (FOR-1055) forrest.echo propery is always true if not commented out

2008-11-13T16:32:44Z

[ https://issues.apache.org/jira/browse/FOR-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647483#action_12647483 ]

David Crossley commented on FOR-1055:
-------------------------------------

Are you sure Gavin? There are other properties (e.g. forrest.validate) that can be set to either true or false. Our Ant build files handle this. Perhaps this forrest.echo property is not being handled consistently like the other properties.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.