> -----Original Message----- > From: Thorsten Scherler [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 13 March 2007 10:57 AM > To: dev@forrest.apache.org > Subject: RE: ForrestBot build for forrest-seed FAILED > > On Mon, 2007-03-12 at 07:54 +0900, Gav.... wrote: > > > > > -----Original Message----- > > > From: Thorsten Scherler [mailto:[EMAIL PROTECTED] > > > Sent: Monday, 12 March 2007 4:09 AM > > > To: dev@forrest.apache.org > > > Subject: RE: ForrestBot build for forrest-seed FAILED > > > > > > On Thu, 2007-03-08 at 21:34 +0900, Gav.... wrote: > > > > > > > > > -----Original Message----- > > > > > From: Ross Gardler [mailto:[EMAIL PROTECTED] > > > > > Sent: Thursday, 8 March 2007 6:35 PM > > > > > To: dev@forrest.apache.org > > > > > Subject: Re: ForrestBot build for forrest-seed FAILED > > > > > > > > > > [EMAIL PROTECTED] wrote: > > > > > > Automated build for forrest-seed FAILED > > > > > > > > > > ... > > > > > > > > > > > [java] X [0] > > > > > pluginDocs/plugins_0_70/error:site:plugins/using BROKEN: No > pipeline > > > > > matched request: pluginDocs/plugins_0_70/error:site:plugins/using > > > > > > > > > > That was the reason for hard coded paths in the plugin docs. I > think > > > > > there is an issue somewhere about this. > > > > > > > > > > Ross > > > > > > > > Only thing I could find was > https://issues.apache.org/jira/browse/FOR- > > > 675 > > > > Seems to be it (also FOR-303) > > > > > > > > > We have to fix this ASAP. > > > > > > The quick fix for now is to disable the cron job (AFAIR David is the > > > owner) OR, which is preferable, to fix the linking! I guess the only > > > thing that is missing is to add site:plugins/using to the site.xml. > > > > > > If nobody will do it, I will try to do it the next week but it would > be > > > nice if more people dig into thus things and fix it. We need more > > > committer that can fix this, it cannot be always David and/or somebody > > > else (normally Ross or me) that dig in (yes we all need time to > > > understand and debug the things, but as more you do the faster you > get). > > > > > > I will, if nobody beats me to it (which I honestly hope someone will), > > > add site:plugins/using to the site.xml of both templates. > > > > In the site.xml of site-author we already have > > > > <plugins label="0.80 Plugins" href="pluginDocs/plugins_0_80/" > > tab="p0_80"> > > <index label="Index" href="index.html"/> > > <using label="Using Plugins" href="usingPlugins.html"/> > > <infrastructure label="Plugin Infrastructure" > > href="pluginInfrastructure.html"/> > > </plugins> > > > > And > > > > <plugins label="0.70 Plugins" href="pluginDocs/plugins_0_70/" > > tab="p0_70"> > > <index label="Index" href="index.html"/> > > <using label="Using Plugins" href="usingPlugins.html"/> > > <infrastructure label="Plugin Infrastructure" > > href="pluginInfrastructure.html"/> > > </plugins> > > > > > > So where else should I be looking? > > The zones example is based on the fresh site. There is neither a link > nor a document for such linking in it. > > Ross provided > http://svn.apache.org/viewvc/forrest/trunk/main/webapp/resources/styleshee > ts/plugins-to-xdoc.xsl?r1=515849&r2=515848&pathrev=515849 > > The question that raises is ask by David commit message: "Replace > hard-coded URL to old usingPlugins doc with site: reference. > Note: Was there a reason for this?" > > The answer gives us the forrestbot by failing. > > I guess we should reverted like suggested by Ross.
Ok , I've had another look now. We know the problem is due to the link not appearing in the site.xml file. Reverting the change will revert it for all webapp sites , yes? So we can A) Revert as suggested. B) Add a full URI to a site.xml entry instead for the test sites. I like B better because it is a workaround to only the affected builds, and leaves others intact and using it properly. The problem has only arisen really because we have included a 'Plugins' tab and a label to only the plugins index page, within the sample sites. Maybe another answer is to either 1. include all information on Plugins in the sample sites, meaning the usingPlugins and pluginInfrastructure pages are there too, providing a complete set of information. 2. Remove the Plugins Tab and Index entry from the sample sites. I don't mind either of these as another option to B. If someone wants to revert Davids change, fine go ahead, I don't like it, but I am only one voice :) If anyone likes any of my preferences, I will apply whichever one suits best. Gav... > > salu2 > -- > Thorsten Scherler thorsten.at.apache.org > Open Source Java & XML consulting, training and solutions
