> -----Original Message----- > From: Gavin [mailto:[EMAIL PROTECTED] > Sent: Sunday, 21 September 2008 12:47 PM > To: dev@forrest.apache.org > Subject: RE: [STATUS] [heads-up] merging our branch Cocoon-2.1 > > > > > -----Original Message----- > > From: Thorsten Scherler [mailto:[EMAIL PROTECTED] > > Sent: Friday, 12 September 2008 8:45 AM > > To: dev@forrest.apache.org > > Subject: Re: [STATUS] [heads-up] merging our branch Cocoon-2.1 > > > > On Thu, 2008-09-11 at 23:22 +0100, Ross Gardler wrote: > > > Why do these things always occur at critical times? > > > > Because it seems we failed to test on windows in the branch. > > > > David reports > > > Ubuntu - okay > > > Mac OS X Tiger - okay > > > Solaris10 - okay > > > > Gavin tested and reported a fail and yourself confirmed that now. > > > > Ideally that have been spotted this problem in the branch and fixed it > > there - not breaking trunk. Ideally. > > > > Many of us are not using windows at all that makes testing on windows so > > much harder. Need to install vmware again. > > > > Will now review Gavins mail again. > > I installed VMWare, now I have a dedicated Windows with the Forrest Trunk > installed (forrest_new). My other machine has the older currently working > with windows version (forrest_old). > > I have done some scenarios, and basically they are that on both the > forrest_old and forrest_new the conclusion is the same - plugins do not > seem > to work on forrest_new whether generated originally from forrest_new or > forrest_old. > > forrest_old generated sites (including seed-basic and seed-sample) WILL > work > on forrest_new (trunk) as long as ONLY the PDF plugin is enabled. ANY > other > plugins will break forrest. > > Not has time to test much further yet.
To expand a little, doing forrest run on a site and you can navigate all the html pages no problem, but as soon as you request a page that involves a plugin - such as .odt, .pod, .txt, whatever it will generate the error earlier described -- except the .pdf which still works fine. Doing a forrest run on a dispatcher site will fails right away dur to the plugin being in use even for html pages. Doing a 'forrest' or 'forrest site' on any site that only involves the pdf plugin will work fine for both forrest_old and forrest_new generated sites when run against the forrest_new trunk. Involve any other plugins whether generated with forrest_old or forrest_new will fail with forrest_new. Sites generated with forrest_new will build against forrest_old. I looked through and there seems to be no difference in the generated sites, it is only the involvement of plugins which break things. I hope this narrows it down a little and that it is not a wild goose chase. > > Gav... > > > > > salu2 > > -- > > Thorsten Scherler thorsten.at.apache.org > > Open Source Java consulting, training and solutions > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG. > > Version: 7.5.524 / Virus Database: 270.6.17/1657 - Release Date: > 9/6/2008 > > 8:07 PM > > > -- > Internal Virus Database is out-of-date. > Checked by AVG. > Version: 7.5.524 / Virus Database: 270.6.21 - Release Date: 9/11/2008 > 12:00 AM
