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 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\resources\stylesheets\svn-to-revision.xsl > (El nombre de archivo, el nombre de directorio o la sintaxis de la > etiqueta del volumen no son correctos)">log.svn-revision.xml</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\resources\stylesheets\svn-to-changes.xsl > (El nombre de archivo, el nombre de directorio o la sintaxis de la > etiqueta del volumen no son correctos)">log.svn.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\resources\stylesheets\svn-log.xsl (El > nombre de archivo, el nombre de directorio o la sintaxis de la > etiqueta del volumen no son correctos)">log.svn-sh.xml</link> > </broken-links>
Thanks for following through. I think that we might now have it. The input.xmap was using staight relative pathnames to those stylesheets. This worked fine on UNIX, but it seems not on Windows. I changed it in r1625483 to use the locationmap. > >> > 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. -David > >> > By the way, this FAQ explains how to run the plugins docs > >> > server on the default 8888 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 > > So things are better now: > > - the projectInfo plugin doesn't work > - the dispatcher info is still outdated but the dispatcher plugin > seems to work fine now > > Vicent > -- > Share what you know, learn what you don't. >