Re: Building my website with forrest 0.9

2014-09-18 Thread Vicent Mas
On Wed, Sep 17, 2014 at 10:29 AM, David Crossley cross...@apache.org wrote:
 On Tue, Sep 16, 2014 at 10:42:11AM +0200, Vicent Mas wrote:
 On Mon, Sep 15, 2014 at 11:16 AM, David Crossley cross...@apache.org wrote:
  On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
  On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
   On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
   wrote:
On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 4:53 PM, David Crossley 
cross...@apache.org wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
 cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration 
  file.
  Then do the 'forrest' command again.

 That fails.

 With the 0.10 version my website is built both with the skinner 
 method
 and with the dispatcher plugin so I think my best option is to 
 use the
 0.10 version and try to find out why the customizations are 
 ignored.

 Thanks again for your help.

 Ah, good that it works with 0.10-dev

 So that confirms https://issues.apache.org/jira/browse/FOR-1188

 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.

 cd 
 $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site
   
It fails for me. The content of the broken-links.xml file is:
   
broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
   
 [snipped some other similar ones for brevity]
   
/broken-links
   
Sorry for not doing this yesterday. I just forgot about it.
   
Thanks. So it seems like the same problem.
  
   I made the change to the projectInfo plugin today to hopefully
   apply the workaround described in FOR-1108 and FOR-1188.
  
   Would you please do 'svn up' and try that plugin again,
   enabled for the Dispatcher.
 
  Hi,
   it fails again. But the content of  broken-links.xml is much shorter
  now (only 2 errors)::
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)index.html/link
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)/index.html/link
  /broken-links
 
  Ah. This plugin is one of the few that utilises a map:mount
  to include a sub-sitemap (Dispatcher too).
 
  I now made another fix to this plugin to stop mounting
  and just add the pipelines from svnHelp.xmap into input.xmap file.
 
  Before doing 'svn up' would you please try this projectInfo
  docs again, but not enabled for the Dispatcher, i.e. just
  with its default skins. I want to see if the problem was
  only with Dispatcher-enabled sites.

 Doing that the broken-links.xml seems to be the same:

 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links

 After doing svn update 

Re: Building my website with forrest 0.9

2014-09-18 Thread David Crossley
Also try again the Dispatcher plugin's docs.
It uses the projectInfo plugin and so hopefully it
now works for you too.
  
   The projectInfo plugin fails so the dispatcher plugin fails too.
  
   Yep.
 
  After doing the svn update the dispatcher plugin is built properly and
  I can see the docs on my web browser.
 
  Great. That is because although it uses the projectInfo plugin,
  it does not use those resources that were missing above.
 
Each plugin's own docs (do 'forrest run' there) is supposed
to demonstrate its own features. So you might be able to follow
its setup and apply to your own situation.
 
  Now hopefully you can get further with that.
 
 Unfortunately I've not been able to make my website work with the
 dispatcher. The plugin works now but its documentation is still
 outdated. I'm studying the plugin and trying to find out how it has to
 be used but I'm failing.

Apart from investigating the Dispatcher plugin's own docs,
there are a couple of other recent-ish plugins that use the Dispatcher.
There is a table in the file $FORREST_HOME/etc/review-plugin-deployment.txt
Look for plugins that were added in v0.9 or more and use the Dispatcher,
for example the input.foaf and input.skos plugins.

 This thread is very long so I will ask for
 help in the thread Customizing a website using forrest 0.10-dev and
 dispatcher
 
 Thanks a lot for all your help.

Thanks to you too. Hope that it gets sorted out.

-David


Re: Building my website with forrest 0.9

2014-09-17 Thread David Crossley
On Tue, Sep 16, 2014 at 10:42:11AM +0200, Vicent Mas wrote:
 On Mon, Sep 15, 2014 at 11:16 AM, David Crossley cross...@apache.org wrote:
  On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
  On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
   On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
   wrote:
On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 4:53 PM, David Crossley 
cross...@apache.org wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
 cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration 
  file.
  Then do the 'forrest' command again.

 That fails.

 With the 0.10 version my website is built both with the skinner 
 method
 and with the dispatcher plugin so I think my best option is to 
 use the
 0.10 version and try to find out why the customizations are 
 ignored.

 Thanks again for your help.

 Ah, good that it works with 0.10-dev

 So that confirms https://issues.apache.org/jira/browse/FOR-1188

 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.

 cd 
 $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site
   
It fails for me. The content of the broken-links.xml file is:
   
broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
   
 [snipped some other similar ones for brevity]
   
/broken-links
   
Sorry for not doing this yesterday. I just forgot about it.
   
Thanks. So it seems like the same problem.
  
   I made the change to the projectInfo plugin today to hopefully
   apply the workaround described in FOR-1108 and FOR-1188.
  
   Would you please do 'svn up' and try that plugin again,
   enabled for the Dispatcher.
 
  Hi,
   it fails again. But the content of  broken-links.xml is much shorter
  now (only 2 errors)::
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)index.html/link
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)/index.html/link
  /broken-links
 
  Ah. This plugin is one of the few that utilises a map:mount
  to include a sub-sitemap (Dispatcher too).
 
  I now made another fix to this plugin to stop mounting
  and just add the pipelines from svnHelp.xmap into input.xmap file.
 
  Before doing 'svn up' would you please try this projectInfo
  docs again, but not enabled for the Dispatcher, i.e. just
  with its default skins. I want to see if the problem was
  only with Dispatcher-enabled sites.
 
 Doing that the broken-links.xml seems to be the same:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links
 
 After doing svn update the built fails with the following errors:
 
 broken-links
   link 

Re: Building my website with forrest 0.9

2014-09-16 Thread Vicent Mas
On Mon, Sep 15, 2014 at 11:16 AM, David Crossley cross...@apache.org wrote:
 On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
 On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
  On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
   wrote:
On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
cross...@apache.org wrote:

 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.
   
That fails.
   
With the 0.10 version my website is built both with the skinner 
method
and with the dispatcher plugin so I think my best option is to use 
the
0.10 version and try to find out why the customizations are ignored.
   
Thanks again for your help.
   
Ah, good that it works with 0.10-dev
   
So that confirms https://issues.apache.org/jira/browse/FOR-1188
   
Would you please try with the projectInfo plugin.
It has been difficult to get someone on Windows to confirm
that it still has that problem.
   
cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
Enable it for Dispatcher in forrest.properties, i.e.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
Then do:
 forrest site
  
   It fails for me. The content of the broken-links.xml file is:
  
   broken-links
 link message=C:\Users\Vicente\Apache
   Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
   Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
   Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
   (El nombre de archivo, el nombre de directorio o la sintaxis de la
   etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
  
[snipped some other similar ones for brevity]
  
   /broken-links
  
   Sorry for not doing this yesterday. I just forgot about it.
  
   Thanks. So it seems like the same problem.
 
  I made the change to the projectInfo plugin today to hopefully
  apply the workaround described in FOR-1108 and FOR-1188.
 
  Would you please do 'svn up' and try that plugin again,
  enabled for the Dispatcher.

 Hi,
  it fails again. But the content of  broken-links.xml is much shorter
 now (only 2 errors)::
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links

 Ah. This plugin is one of the few that utilises a map:mount
 to include a sub-sitemap (Dispatcher too).

 I now made another fix to this plugin to stop mounting
 and just add the pipelines from svnHelp.xmap into input.xmap file.

 Before doing 'svn up' would you please try this projectInfo
 docs again, but not enabled for the Dispatcher, i.e. just
 with its default skins. I want to see if the problem was
 only with Dispatcher-enabled sites.


Doing that the broken-links.xml seems to be the same:

broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
nombre de directorio o la sintaxis de la etiqueta del volumen no son
correctos)index.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
nombre de directorio o la sintaxis de la etiqueta del volumen no son
correctos)/index.html/link
/broken-links

After doing svn update the built fails with the following errors:

broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache

Re: Building my website with forrest 0.9

2014-09-15 Thread Vicent Mas
On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org wrote:
 On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
 On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
  wrote:
   On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
   wrote:
   
If that works, then try configuring that sample site
to use Dispatcher. See its forrest.properties configuration file.
Then do the 'forrest' command again.
  
   That fails.
  
   With the 0.10 version my website is built both with the skinner method
   and with the dispatcher plugin so I think my best option is to use the
   0.10 version and try to find out why the customizations are ignored.
  
   Thanks again for your help.
  
   Ah, good that it works with 0.10-dev
  
   So that confirms https://issues.apache.org/jira/browse/FOR-1188
  
   Would you please try with the projectInfo plugin.
   It has been difficult to get someone on Windows to confirm
   that it still has that problem.
  
   cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
   Enable it for Dispatcher in forrest.properties, i.e.
   project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
   Then do:
forrest site
 
  It fails for me. The content of the broken-links.xml file is:
 
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
  (El nombre de archivo, el nombre de directorio o la sintaxis de la
  etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
 
   [snipped some other similar ones for brevity]
 
  /broken-links
 
  Sorry for not doing this yesterday. I just forgot about it.
 
  Thanks. So it seems like the same problem.

 I made the change to the projectInfo plugin today to hopefully
 apply the workaround described in FOR-1108 and FOR-1188.

 Would you please do 'svn up' and try that plugin again,
 enabled for the Dispatcher.


Hi,
 it fails again. But the content of  broken-links.xml is much shorter
now (only 2 errors)::
broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
nombre de directorio o la sintaxis de la etiqueta del volumen no son
correctos)index.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
nombre de directorio o la sintaxis de la etiqueta del volumen no son
correctos)/index.html/link
/broken-links

 Also try again the Dispatcher plugin's docs.
 It uses the projectInfo plugin and so hopefully it
 now works for you too.


The projectInfo plugin fails so the dispatcher plugin fails too.

 Each plugin's own docs (do 'forrest run' there) is supposed
 to demonstrate its own features. So you might be able to follow
 its setup and apply to your own situation.

 By the way, this FAQ explains how to run the plugins docs
 server on the default  port and your project on another port:
 http://forrest.apache.org/docs_0_100/faq.html#run_port


I didn't know it. Thanks for the info

  Getting back to your own website.
  Do you use any other plugins, or just Dispatcher?

 I use the PDF plugin too, if the site is not built. It seems that the
 dispatcher requires the PDF plugin.


The above lines should read:

I use the PDF plugin too, if *not* the site is not built. It seems that the
dispatcher requires the PDF plugin.

Vicent

-- 
Share what you know, learn what you don't.


Re: Building my website with forrest 0.9

2014-09-15 Thread David Crossley
On Mon, Sep 15, 2014 at 10:21:41AM +0200, Vicent Mas wrote:
 On Sun, Sep 14, 2014 at 10:54 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
  On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org 
  wrote:
   On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
   wrote:
On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
On Thu, Sep 11, 2014 at 2:54 AM, David Crossley 
cross...@apache.org wrote:

 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.
   
That fails.
   
With the 0.10 version my website is built both with the skinner 
method
and with the dispatcher plugin so I think my best option is to use 
the
0.10 version and try to find out why the customizations are ignored.
   
Thanks again for your help.
   
Ah, good that it works with 0.10-dev
   
So that confirms https://issues.apache.org/jira/browse/FOR-1188
   
Would you please try with the projectInfo plugin.
It has been difficult to get someone on Windows to confirm
that it still has that problem.
   
cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
Enable it for Dispatcher in forrest.properties, i.e.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
Then do:
 forrest site
  
   It fails for me. The content of the broken-links.xml file is:
  
   broken-links
 link message=C:\Users\Vicente\Apache
   Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
   Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
   Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
   (El nombre de archivo, el nombre de directorio o la sintaxis de la
   etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
  
[snipped some other similar ones for brevity]
  
   /broken-links
  
   Sorry for not doing this yesterday. I just forgot about it.
  
   Thanks. So it seems like the same problem.
 
  I made the change to the projectInfo plugin today to hopefully
  apply the workaround described in FOR-1108 and FOR-1188.
 
  Would you please do 'svn up' and try that plugin again,
  enabled for the Dispatcher.
 
 Hi,
  it fails again. But the content of  broken-links.xml is much shorter
 now (only 2 errors)::
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)index.html/link
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)/index.html/link
 /broken-links

Ah. This plugin is one of the few that utilises a map:mount
to include a sub-sitemap (Dispatcher too).

I now made another fix to this plugin to stop mounting
and just add the pipelines from svnHelp.xmap into input.xmap file.

Before doing 'svn up' would you please try this projectInfo
docs again, but not enabled for the Dispatcher, i.e. just
with its default skins. I want to see if the problem was
only with Dispatcher-enabled sites.

  Also try again the Dispatcher plugin's docs.
  It uses the projectInfo plugin and so hopefully it
  now works for you too.
 
 The projectInfo plugin fails so the dispatcher plugin fails too.

Yep.

  Each plugin's own docs (do 'forrest run' there) is supposed
  to demonstrate its own features. So you might be able to follow
  its setup and apply to your own situation.
 
  By the way, this FAQ explains how to run the plugins docs
  server on the default  port and your project on another port:
  http://forrest.apache.org/docs_0_100/faq.html#run_port
 
 I didn't know it. Thanks for the info
 
   Getting back to your own website.
   Do you use any other plugins, or just Dispatcher?
 
  I use the PDF plugin too, if the site is not built. It seems that the
  dispatcher requires the PDF plugin.
 
 The above lines should read:
 
 I use the PDF plugin too, if *not* the site is not built. It seems that the
 dispatcher requires the PDF plugin.

Yes i figured out what you meant, but i did not understand why.

I see now. It is because the default settings for the Dispatcher
do add a link to *.pdf for each page.

-David


Re: Building my website with forrest 0.9

2014-09-14 Thread David Crossley
On Fri, Sep 12, 2014 at 11:03:58AM +0200, Vicent Mas wrote:
 On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org wrote:
  On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org 
  wrote:
   On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
   On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
   wrote:
   
If that works, then try configuring that sample site
to use Dispatcher. See its forrest.properties configuration file.
Then do the 'forrest' command again.
  
   That fails.
  
   With the 0.10 version my website is built both with the skinner method
   and with the dispatcher plugin so I think my best option is to use the
   0.10 version and try to find out why the customizations are ignored.
  
   Thanks again for your help.
  
   Ah, good that it works with 0.10-dev
  
   So that confirms https://issues.apache.org/jira/browse/FOR-1188
  
   Would you please try with the projectInfo plugin.
   It has been difficult to get someone on Windows to confirm
   that it still has that problem.
  
   cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
   Enable it for Dispatcher in forrest.properties, i.e.
   project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
   Then do:
forrest site
 
  It fails for me. The content of the broken-links.xml file is:
 
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
  Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
  (El nombre de archivo, el nombre de directorio o la sintaxis de la
  etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
 
   [snipped some other similar ones for brevity]
 
  /broken-links
 
  Sorry for not doing this yesterday. I just forgot about it.
 
  Thanks. So it seems like the same problem.

I made the change to the projectInfo plugin today to hopefully
apply the workaround described in FOR-1108 and FOR-1188.

Would you please do 'svn up' and try that plugin again,
enabled for the Dispatcher.

Also try again the Dispatcher plugin's docs.
It uses the projectInfo plugin and so hopefully it
now works for you too.

Each plugin's own docs (do 'forrest run' there) is supposed
to demonstrate its own features. So you might be able to follow
its setup and apply to your own situation.

By the way, this FAQ explains how to run the plugins docs
server on the default  port and your project on another port:
http://forrest.apache.org/docs_0_100/faq.html#run_port

  Getting back to your own website.
  Do you use any other plugins, or just Dispatcher?
 
 I use the PDF plugin too, if the site is not built. It seems that the
 dispatcher requires the PDF plugin.

I cannot understand why that would be so.

-David


Re: Building my website with forrest 0.9

2014-09-12 Thread Vicent Mas
On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration file.
  Then do the 'forrest' command again.

 That fails.

 With the 0.10 version my website is built both with the skinner method
 and with the dispatcher plugin so I think my best option is to use the
 0.10 version and try to find out why the customizations are ignored.

 Thanks again for your help.

 Ah, good that it works with 0.10-dev

 So that confirms https://issues.apache.org/jira/browse/FOR-1188

 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.

 cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site

It fails for me. The content of the broken-links.xml file is:

broken-links
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)releaseNotes_0.2.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son
correctos)docs/user/useCases/useCaseFeatures.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son
correctos)docs/user/useCases/changeLogFeatures.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)todo.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son
correctos)docs/developer/useCases/changeLogFeatures.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)releaseNotes_0.1.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son
correctos)docs/developer/useCases/useCaseFeatures.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\svnHelper.xmap (El nombre de archivo, el
nombre de directorio o la sintaxis de la etiqueta del volumen no son
correctos)index.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
(El nombre de archivo, el nombre de directorio o la sintaxis de la
etiqueta del volumen no son correctos)changes.html/link
  link message=C:\Users\Vicente\Apache
Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache

Re: Building my website with forrest 0.9

2014-09-12 Thread David Crossley
On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org wrote:
  On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
  wrote:
  
   If that works, then try configuring that sample site
   to use Dispatcher. See its forrest.properties configuration file.
   Then do the 'forrest' command again.
 
  That fails.
 
  With the 0.10 version my website is built both with the skinner method
  and with the dispatcher plugin so I think my best option is to use the
  0.10 version and try to find out why the customizations are ignored.
 
  Thanks again for your help.
 
  Ah, good that it works with 0.10-dev
 
  So that confirms https://issues.apache.org/jira/browse/FOR-1188
 
  Would you please try with the projectInfo plugin.
  It has been difficult to get someone on Windows to confirm
  that it still has that problem.
 
  cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
  Enable it for Dispatcher in forrest.properties, i.e.
  project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
  Then do:
   forrest site
 
 It fails for me. The content of the broken-links.xml file is:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
 (El nombre de archivo, el nombre de directorio o la sintaxis de la
 etiqueta del volumen no son correctos)releaseNotes_0.2.html/link

 [snipped some other similar ones for brevity]

 /broken-links
 
 Sorry for not doing this yesterday. I just forgot about it.

Thanks. So it seems like the same problem.

Getting back to your own website.
Do you use any other plugins, or just Dispatcher?

-David


Re: Building my website with forrest 0.9

2014-09-12 Thread Vicent Mas
On Fri, Sep 12, 2014 at 10:45 AM, David Crossley cross...@apache.org wrote:
 On Fri, Sep 12, 2014 at 10:28:34AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 4:53 PM, David Crossley cross...@apache.org wrote:
  On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org 
  wrote:
  
   If that works, then try configuring that sample site
   to use Dispatcher. See its forrest.properties configuration file.
   Then do the 'forrest' command again.
 
  That fails.
 
  With the 0.10 version my website is built both with the skinner method
  and with the dispatcher plugin so I think my best option is to use the
  0.10 version and try to find out why the customizations are ignored.
 
  Thanks again for your help.
 
  Ah, good that it works with 0.10-dev
 
  So that confirms https://issues.apache.org/jira/browse/FOR-1188
 
  Would you please try with the projectInfo plugin.
  It has been difficult to get someone on Windows to confirm
  that it still has that problem.
 
  cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
  Enable it for Dispatcher in forrest.properties, i.e.
  project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
  Then do:
   forrest site

 It fails for me. The content of the broken-links.xml file is:

 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\Apache
 Forrest\forrest\plugins\org.apache.forrest.plugin.input.projectInfo\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\org.apache.forrest.plugin.input.projectInfo
 (El nombre de archivo, el nombre de directorio o la sintaxis de la
 etiqueta del volumen no son correctos)releaseNotes_0.2.html/link

  [snipped some other similar ones for brevity]

 /broken-links

 Sorry for not doing this yesterday. I just forgot about it.

 Thanks. So it seems like the same problem.

 Getting back to your own website.
 Do you use any other plugins, or just Dispatcher?

 -David

Hi,

I use the PDF plugin too, if the site is not built. It seems that the
dispatcher requires the PDF plugin.

Vicent

-- 
Share what you know, learn what you don't.


Re: Building my website with forrest 0.9

2014-09-11 Thread David Crossley
On Thu, Sep 11, 2014 at 10:54:29AM +1000, David Crossley wrote:
 On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
  Hi,
  
  I've just installed forrest-0.9 with the help of David Crossley (thanks 
  again).
  
  Unfortunately it can't build my website (that I built when 0.9 was the
  developer version).
  With 'forrest run' I get the following error:
  
  Internal Server Error
  Message: null
  Description: No details available.
  Sender: org.apache.cocoon.servlet.CocoonServlet
  Source: Cocoon Servlet
  cause
  
  C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)
  
  request-uri
  /index.html
  
  Request URI
  index.html
 
  If I do a clean, run 'forrest' and read the broken-links.xml file it says:
  
  broken-links
link message=C:\Users\Vicente\Apache
  Forrest\forrest\main\webapp\.\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
  Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
  nombre de directorio o la sintaxis de la etiqueta del volumen no son
  correctos)linkmap.html/link
  /broken-links
  
  I don't know what to do now. Any ideas?
 
 Those mangled Windows pathnames are certainly a problem.

This Google search: apache forrest mangled Windows
found some relevant past discussion. There is dev list stuff,
plus two issues:
https://issues.apache.org/jira/browse/FOR-1108
 Dispatcher, Cocoon 2.1 and Windows
https://issues.apache.org/jira/browse/FOR-1188
 locationmap or sitemap path broken on Windows, multiple paths concatenated

These sound similar to your problems.

 First thing is to ensure that a default skinned site will work.
 In a new directory, do:
  forrest seed-sample
  forrest
 
 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.
 
  Should I try forrest 0.10?
 
 Perhaps that might help.

In the FOR-1188 issue listed above, Sjur seemed to indicate
that using svn trunk (forrest-0.10-dev) did help.

It would be great to finish investigating those issues
and hopefully remove the workarounds.

-David

 I do recall some similar issues in the past.
 I do not use Windows, so it is difficult for me to help.
 Let us hope that one of the other committers that use
 Dispatcher will assist.
 
 -David
 
  TIA
  
  Vicent
  
  PS: I'm using Windows 8.1 (and missing my Ubuntu)
  
  -- 
  Share what you know, learn what you don't.
  


Re: Building my website with forrest 0.9

2014-09-11 Thread Vicent Mas
On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
 On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,

 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).

 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).
 With 'forrest run' I get the following error:

 Internal Server Error
 Message: null
 Description: No details available.
 Sender: org.apache.cocoon.servlet.CocoonServlet
 Source: Cocoon Servlet
 cause

 C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)

 request-uri
 /index.html

 Request URI
 index.html

 If I do a clean, run 'forrest' and read the broken-links.xml file it says:

 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)linkmap.html/link
 /broken-links

 I don't know what to do now. Any ideas?

 Those mangled Windows pathnames are certainly a problem.

 First thing is to ensure that a default skinned site will work.
 In a new directory, do:
  forrest seed-sample
  forrest


That works.

 If that works, then try configuring that sample site
 to use Dispatcher. See its forrest.properties configuration file.
 Then do the 'forrest' command again.


That fails.

With the 0.10 version my website is built both with the skinner method
and with the dispatcher plugin so I think my best option is to use the
0.10 version and try to find out why the customizations are ignored.

Thanks again for your help.



-- 
Share what you know, learn what you don't.


Re: Building my website with forrest 0.9

2014-09-11 Thread Vicent Mas
On Thu, Sep 11, 2014 at 3:43 AM, David Crossley cross...@apache.org wrote:
 On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,

 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).

 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).

 If you are referring just to the ViTables site
 (that is listed here http://forrest.apache.org/live-sites.html#dispatcher)
 then i do not see the need for using Dispatcher,
 as that seems to be a straight-forward website.

 -David

Yes, I'm referring to the ViTables site.

Maybe you're right and it is simple but I don't how to do some of the
wanted customizations using the skinconf.xml file. For instance I
don't know how to have two copyright lines instead of just one or how
to use the lightbox javascript only in the screenshots page or how to
show the site-info credits in every page of the site instead of just
in the welcome page. However I managed t do this customizations via
dispatcher and contracts customization. This is why I've used the
dispatcher. A secondary reason is that when reading about the
dispatcher plugin I got the sensation that it would be the recommended
customization way in the future.

Vicent

-- 
Share what you know, learn what you don't.


Re: Building my website with forrest 0.9

2014-09-11 Thread David Crossley
On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
 On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
 
  If that works, then try configuring that sample site
  to use Dispatcher. See its forrest.properties configuration file.
  Then do the 'forrest' command again.
 
 That fails.
 
 With the 0.10 version my website is built both with the skinner method
 and with the dispatcher plugin so I think my best option is to use the
 0.10 version and try to find out why the customizations are ignored.
 
 Thanks again for your help.

Ah, good that it works with 0.10-dev

So that confirms https://issues.apache.org/jira/browse/FOR-1188

Would you please try with the projectInfo plugin.
It has been difficult to get someone on Windows to confirm
that it still has that problem.

cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
Enable it for Dispatcher in forrest.properties, i.e.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
Then do:
 forrest site

-David


Re: Building my website with forrest 0.9

2014-09-11 Thread David Crossley
On Fri, Sep 12, 2014 at 12:53:49AM +1000, David Crossley wrote:
 On Thu, Sep 11, 2014 at 11:24:16AM +0200, Vicent Mas wrote:
  On Thu, Sep 11, 2014 at 2:54 AM, David Crossley cross...@apache.org wrote:
  
   If that works, then try configuring that sample site
   to use Dispatcher. See its forrest.properties configuration file.
   Then do the 'forrest' command again.
  
  That fails.
  
  With the 0.10 version my website is built both with the skinner method
  and with the dispatcher plugin so I think my best option is to use the
  0.10 version and try to find out why the customizations are ignored.
  
  Thanks again for your help.
 
 Ah, good that it works with 0.10-dev
 
 So that confirms https://issues.apache.org/jira/browse/FOR-1188
 
 Would you please try with the projectInfo plugin.
 It has been difficult to get someone on Windows to confirm
 that it still has that problem.
 
 cd $FORREST_HOME/plugins/org.apache.forrest.plugin.input.projectInfo/
 Enable it for Dispatcher in forrest.properties, i.e.
 project.required.plugins=org.apache.forrest.plugin.input.projectInfo,org.apache.forrest.plugin.internal.dispatcher
 Then do:
  forrest site

The remnants of this issue might be what is causing your
recent problems in the other discussion thread about
trying to view the local docs for the Dispatcher plugin.

-David


Re: Building my website with forrest 0.9

2014-09-10 Thread David Crossley
On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,
 
 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).
 
 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).
 With 'forrest run' I get the following error:
 
 Internal Server Error
 Message: null
 Description: No details available.
 Sender: org.apache.cocoon.servlet.CocoonServlet
 Source: Cocoon Servlet
 cause
 
 C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)
 
 request-uri
 /index.html
 
 Request URI
 index.html

 If I do a clean, run 'forrest' and read the broken-links.xml file it says:
 
 broken-links
   link message=C:\Users\Vicente\Apache
 Forrest\forrest\main\webapp\.\C:\Users\Vicente\ViTables\Website\forrest\build\tmp\C:\Users\Vicente\Apache
 Forrest\forrest\build\plugins\dataModel.xmap (El nombre de archivo, el
 nombre de directorio o la sintaxis de la etiqueta del volumen no son
 correctos)linkmap.html/link
 /broken-links
 
 I don't know what to do now. Any ideas?

Those mangled Windows pathnames are certainly a problem.

First thing is to ensure that a default skinned site will work.
In a new directory, do:
 forrest seed-sample
 forrest

If that works, then try configuring that sample site
to use Dispatcher. See its forrest.properties configuration file.
Then do the 'forrest' command again.

 Should I try forrest 0.10?

Perhaps that might help.

I do recall some similar issues in the past.
I do not use Windows, so it is difficult for me to help.
Let us hope that one of the other committers that use
Dispatcher will assist.

-David

 TIA
 
 Vicent
 
 PS: I'm using Windows 8.1 (and missing my Ubuntu)
 
 -- 
 Share what you know, learn what you don't.
 


Re: Building my website with forrest 0.9

2014-09-10 Thread David Crossley
On Wed, Sep 10, 2014 at 11:23:07AM +0200, Vicent Mas wrote:
 Hi,
 
 I've just installed forrest-0.9 with the help of David Crossley (thanks 
 again).
 
 Unfortunately it can't build my website (that I built when 0.9 was the
 developer version).

If you are referring just to the ViTables site
(that is listed here http://forrest.apache.org/live-sites.html#dispatcher)
then i do not see the need for using Dispatcher,
as that seems to be a straight-forward website.

-David