You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2006/07/10 12:05:27 UTC
Re: review list of scheduled issues for 0.8 release
I can't believe that two months have flown by since last time
we tried to narrow down the list of issues.
We are down from 47 to 37 issues for filter FOR-roadmap-dev.
http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310820
Last time we just reviewed the Blocker and Critical issues.
This time lets try all 37.
I have added some comments below to explain the status of each.
I tried to identify some that can be moved over to 0.9-dev.
Lazy consensus applies - i will move those over soon. Please
identify others.
------------------------
FOR-867 need doc to explain status of skins and dispatcher
http://issues.apache.org/jira/browse/FOR-867
I started a doc, but it needs more content summarised from
our mailing list discussion about it.
------------------------
FOR-868 add relevant notes to the "Upgrading" xdoc
http://issues.apache.org/jira/browse/FOR-868
Needs to wait for FOR-865.
------------------------
FOR-865 Add missing entries to status.xml to generate the changes list
http://issues.apache.org/jira/browse/FOR-865
I have recently waded through the past commits and added
many missing entries. Next it needs to tune it to move some
entries into the plugins documentation. Also need to set the
importance attribute for some.
------------------------
FOR-855 verify the license situation prior to each release
http://issues.apache.org/jira/browse/FOR-855
Recently i added license headers for all source files
and will do this again closer to the release.
------------------------
FOR-533 Auto Generate plugins.xml entry
http://issues.apache.org/jira/browse/FOR-533
Last time Ross said:
> This should stay in 0.8, it's a fairly minor job, I've done most of the
> preparatory work (I think).
------------------------
FOR-639 define terminology for the various aspects of Dispatcher
http://issues.apache.org/jira/browse/FOR-639
A doc has been started by Gavin. We need more content.
------------------------
FOR-735 Plugins are not correctly deployed in webapp mode
http://issues.apache.org/jira/browse/FOR-735
Investigate.
------------------------
FOR-711 Cache results from the Locationmap
http://issues.apache.org/jira/browse/FOR-711
Last time Ross said:
> OK to go into 0.9, but we will need a FAQ entry explaining how to turn
> caching off for development since with it on we are forced to reboot
> Forrest each time the LM is changed. Tim mentioned in the archives how
> to turn it off.
------------------------
FOR-742 trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
http://issues.apache.org/jira/browse/FOR-742
Test.
------------------------
FOR-241 character entities (e.g. ampersand) are expanded again for href or src attributes
http://issues.apache.org/jira/browse/FOR-241
????
------------------------
FOR-210 whole-site html and pdf: broken link faq, broken image links
http://issues.apache.org/jira/browse/FOR-210
Delay until 0.9-dev.
------------------------
FOR-211 whole-site html and pdf: broken ext links
http://issues.apache.org/jira/browse/FOR-211
Delay until 0.9-dev.
------------------------
FOR-200 Locationmap for Forrest and Users
http://issues.apache.org/jira/browse/FOR-200
This must be getting close. Investigate.
------------------------
FOR-546 Sitemap reference doc should be updated to reflect plugin architecture
http://issues.apache.org/jira/browse/FOR-546
Delay until 0.9-dev.
------------------------
FOR-560 Remove duplicate jars from eclipse plugins
http://issues.apache.org/jira/browse/FOR-560
Delay until 0.9-dev.
------------------------
FOR-644 code-style cleanup for xml files
http://issues.apache.org/jira/browse/FOR-644
Delay until 0.9-dev.
------------------------
FOR-666 clarify the sitemap matches etc. in FAQ about non-skinned html
http://issues.apache.org/jira/browse/FOR-666
Delay until 0.9-dev.
------------------------
FOR-726 use locationmap in all of the plugins
http://issues.apache.org/jira/browse/FOR-726
This must be getting close. Investigate.
------------------------
FOR-721 entries without labels in site.xml are now being crawled and generated
http://issues.apache.org/jira/browse/FOR-721
Delay until 0.9-dev.
------------------------
FOR-677 leading slash in gathered URIs causes double the number of links to be processed
http://issues.apache.org/jira/browse/FOR-677
Document workaround as FAQ.
------------------------
FOR-765 forrest war gets NoSuchMethodError for some core transformer
http://issues.apache.org/jira/browse/FOR-765
Investigate.
------------------------
FOR-772 INvalid HTML as source causes unexpected behaviour
http://issues.apache.org/jira/browse/FOR-772
Document as FAQ.
------------------------
FOR-776 rationalise the pluginTemplate and current plugins to have minimal configuration files, etc.
http://issues.apache.org/jira/browse/FOR-776
Delay until 0.9-dev.
------------------------
FOR-209 First level selected tab is not highlighted when containing 2nd level tabs
http://issues.apache.org/jira/browse/FOR-209
Delay until 0.9-dev.
------------------------
FOR-705 Target of LocationMap rewriteDemo causes build failure when target not available
http://issues.apache.org/jira/browse/FOR-705
Delay until 0.9-dev.
------------------------
FOR-785 plugins/*/skinconf.xml does not validate since using entity to ease management
http://issues.apache.org/jira/browse/FOR-785
Delay until 0.9-dev.
------------------------
FOR-901 Review the note on the home page about first forrest run and retrieving plugins from network
http://issues.apache.org/jira/browse/FOR-901
Do.
------------------------
FOR-203 2nd level tabs are not selected appropriately
http://issues.apache.org/jira/browse/FOR-203
Delay until 0.9-dev.
------------------------
FOR-699 Beginner HowTos for installing Forrest
http://issues.apache.org/jira/browse/FOR-699
Delay until 0.9-dev.
------------------------
FOR-889 Use by Ant of newer catalog entity resolver failing for Windows
http://issues.apache.org/jira/browse/FOR-889
Reported to xml-commons-dev but that is a very quiet list.
It might be an Ant issue. Someone on Windows needs to investigate
Ant-1.6.5 branch for the xmlvalidate/xmlcatalog task's interaction
with entity resolver.
Otherwise delay until 0.9-dev.
------------------------
FOR-537 Plugin documentation sitemap references
http://issues.apache.org/jira/browse/FOR-537
Investigate.
------------------------
FOR-671 Layering error of HTML headings breaks rest of the page w/o warning
http://issues.apache.org/jira/browse/FOR-671
Document as FAQ.
------------------------
FOR-731 empty linkmap.html document, side-effect of workaround to FOR-675
http://issues.apache.org/jira/browse/FOR-731
Investigate.
------------------------
FOR-767 Forrestbot webapp reports succesful even when there are broken links
http://issues.apache.org/jira/browse/FOR-767
Investigate.
------------------------
FOR-861 Update locationmap docs for working with remote files
http://issues.apache.org/jira/browse/FOR-861
Do.
------------------------
FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
http://issues.apache.org/jira/browse/FOR-635
Investigate.
------------------------
FOR-488 Remove Zip Java components from Forrest
http://issues.apache.org/jira/browse/FOR-488
Delay until 0.9-dev.
------------------------
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
...
>>>>> Would developers please try to use the current forrest
>>>>> trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
We need more testing.
...
>>>>> We need reports for various versions of Jetty and Tomcat,
>>>>> so we need multiple developers to help with this testing.
>>>> You already have my success story for Tomcat 6.
Thanks Gav.
...
>>>> I will test it shortly on a dispatcher site.
>>> How did you go?
>> Thanks for the reminder, I just tried it now on a dispatcher site.
...
> And may relate this issue now to
> http://issues.apache.org/jira/browse/FOR-932
Dispatcher is in the whiteboard and so it does not matter if it does not
work in a deployed 0.8 war. As long as it works in the internal Jetty
and works for generating the static site (which it does) then we are goo
to go for 0.8.
I'll link this thread to the above issue and schedule that issue for 0.9.
Ross
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: Gav.... [mailto:brightoncomputers@brightontown.com.au]
> Sent: Thursday, 22 March 2007 6:51 PM
> To: dev@forrest.apache.org
> Subject: RE: testing forrest-0.8 as WAR in Jetty and Tomcat
>
>
>
> > -----Original Message-----
> > From: David Crossley [mailto:crossley@apache.org]
> > Sent: Thursday, 22 March 2007 3:11 PM
> > To: dev@forrest.apache.org
> > Subject: Re: testing forrest-0.8 as WAR in Jetty and Tomcat
> >
> > On Dec 11 2006 Gav.... wrote:
> > > From: David Crossley
> > > > Sent: Thursday, 10 August 2006
> > > >
> > > > Would developers please try to use the current forrest
> > > > trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
> > > >
> > > > Do ...
> > > > cd my-new-directory
> > > > forrest seed-sample war
> > > >
> > > > Then deploy the my-project.war to your servlet container.
> > > >
> > > > Then try it on a site that uses your favourite plugins.
> > > >
> > > > This is needed to progress towards the 0.8 release.
> > > >
> > > > We need reports for various versions of Jetty and Tomcat,
> > > > so we need multiple developers to help with this testing.
> > >
> > > You already have my success story for Tomcat 6.
> >
> > Thanks. See https://issues.apache.org/jira/browse/FOR-765
> >
> > > So I thought
> > > I would try using Jetty.
> > >
> > > 1. - I have downloaded Jetty 6.
> > > 2. - java -jar start.jar etc/jetty.xml etc/jetty.xml
> > > 3. - Localhost:8080 brings up jetty sample site ok
> > > 4. - Download Maven 2
> > > 5. - Build Jetty with Maven 2, Build failed error which
> > > I summised to be
> > >
> >
> http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=70f6a0e1d75ac913d8b
> > 31
> > > fba76c1:YfiG?bug_id=4352234
> > >
> > > ( 4 and 5, I was going to run 'mvn jetty:run' to use the plugin but
> this
> > > Didn't work out.)
> > >
> > > So in the end, using Full Jetty version 6.
> > >
> > > 1. 'forrest war' on a seed-sample site.
> > > 2. Copied WAR file to Jettys /webapp/ directory. (rather than
> configure
> > > files)
> > > 3. java -jar start.jar etc/jetty.xml etc/jetty.xml
> > > 4. http://localhost:8080/my-project/
> > >
> > > All works fine.
> > >
> > > So maybe you are using the forrest jetty or some other way of doing
> it.
> > > Could you guide me through your scenario so I can try it?
> >
> > Yes i meant using a full separate version of Jetty, not Forrest's
> > packaged one which is a cut-down of an old Jetty.
> >
> > I followed your method today, and yes it works for me
> > with Java 5 and Jetty 6.
> >
> > I had been trying with a local configuration and starting
> > Jetty with a shell-script. Perhaps that config was not correct.
> > Anyway just using default config and 'java -jar start.jar etc/jetty.xml'
> > it works.
> >
> > However doing the same with Java 1.4.2 is not working.
> > It gives the error described in FOR-765.
> >
> > > I will test it shortly on a dispatcher site.
> >
> > How did you go?
>
> Thanks for the reminder, I just tried it now on a dispatcher site.
>
> I get :-
>
> Message: null
>
> Description: No details available.
>
> Sender: org.apache.cocoon.servlet.CocoonServlet
>
> Source: Cocoon Servlet
>
> Request URI
>
> index.html
>
> cause
>
> Could not resolve locationmap location.
>
> request-uri
>
> /my-project/index.html
>
>
> This happens for all .html files.
> All .xml files display fine.
>
> Gav...
And may relate this issue now to
http://issues.apache.org/jira/browse/FOR-932
Gav...
>
> >
> > -David
> >
> >
> > --
> > Internal Virus Database is out-of-date.
> > Checked by AVG Free Edition.
> > Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date:
> 3/14/2007
> > 3:38 PM
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
> 3:38 PM
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 22 March 2007 3:11 PM
> To: dev@forrest.apache.org
> Subject: Re: testing forrest-0.8 as WAR in Jetty and Tomcat
>
> On Dec 11 2006 Gav.... wrote:
> > From: David Crossley
> > > Sent: Thursday, 10 August 2006
> > >
> > > Would developers please try to use the current forrest
> > > trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
> > >
> > > Do ...
> > > cd my-new-directory
> > > forrest seed-sample war
> > >
> > > Then deploy the my-project.war to your servlet container.
> > >
> > > Then try it on a site that uses your favourite plugins.
> > >
> > > This is needed to progress towards the 0.8 release.
> > >
> > > We need reports for various versions of Jetty and Tomcat,
> > > so we need multiple developers to help with this testing.
> >
> > You already have my success story for Tomcat 6.
>
> Thanks. See https://issues.apache.org/jira/browse/FOR-765
>
> > So I thought
> > I would try using Jetty.
> >
> > 1. - I have downloaded Jetty 6.
> > 2. - java -jar start.jar etc/jetty.xml etc/jetty.xml
> > 3. - Localhost:8080 brings up jetty sample site ok
> > 4. - Download Maven 2
> > 5. - Build Jetty with Maven 2, Build failed error which
> > I summised to be
> >
> http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=70f6a0e1d75ac913d8b
> 31
> > fba76c1:YfiG?bug_id=4352234
> >
> > ( 4 and 5, I was going to run 'mvn jetty:run' to use the plugin but this
> > Didn't work out.)
> >
> > So in the end, using Full Jetty version 6.
> >
> > 1. 'forrest war' on a seed-sample site.
> > 2. Copied WAR file to Jettys /webapp/ directory. (rather than configure
> > files)
> > 3. java -jar start.jar etc/jetty.xml etc/jetty.xml
> > 4. http://localhost:8080/my-project/
> >
> > All works fine.
> >
> > So maybe you are using the forrest jetty or some other way of doing it.
> > Could you guide me through your scenario so I can try it?
>
> Yes i meant using a full separate version of Jetty, not Forrest's
> packaged one which is a cut-down of an old Jetty.
>
> I followed your method today, and yes it works for me
> with Java 5 and Jetty 6.
>
> I had been trying with a local configuration and starting
> Jetty with a shell-script. Perhaps that config was not correct.
> Anyway just using default config and 'java -jar start.jar etc/jetty.xml'
> it works.
>
> However doing the same with Java 1.4.2 is not working.
> It gives the error described in FOR-765.
>
> > I will test it shortly on a dispatcher site.
>
> How did you go?
Thanks for the reminder, I just tried it now on a dispatcher site.
I get :-
Message: null
Description: No details available.
Sender: org.apache.cocoon.servlet.CocoonServlet
Source: Cocoon Servlet
Request URI
index.html
cause
Could not resolve locationmap location.
request-uri
/my-project/index.html
This happens for all .html files.
All .xml files display fine.
Gav...
>
> -David
>
>
> --
> Internal Virus Database is out-of-date.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.11/722 - Release Date: 3/14/2007
> 3:38 PM
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
On Dec 11 2006 Gav.... wrote:
> From: David Crossley
> > Sent: Thursday, 10 August 2006
> >
> > Would developers please try to use the current forrest
> > trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
> >
> > Do ...
> > cd my-new-directory
> > forrest seed-sample war
> >
> > Then deploy the my-project.war to your servlet container.
> >
> > Then try it on a site that uses your favourite plugins.
> >
> > This is needed to progress towards the 0.8 release.
> >
> > We need reports for various versions of Jetty and Tomcat,
> > so we need multiple developers to help with this testing.
>
> You already have my success story for Tomcat 6.
Thanks. See https://issues.apache.org/jira/browse/FOR-765
> So I thought
> I would try using Jetty.
>
> 1. - I have downloaded Jetty 6.
> 2. - java -jar start.jar etc/jetty.xml etc/jetty.xml
> 3. - Localhost:8080 brings up jetty sample site ok
> 4. - Download Maven 2
> 5. - Build Jetty with Maven 2, Build failed error which
> I summised to be
> http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=70f6a0e1d75ac913d8b31
> fba76c1:YfiG?bug_id=4352234
>
> ( 4 and 5, I was going to run 'mvn jetty:run' to use the plugin but this
> Didn't work out.)
>
> So in the end, using Full Jetty version 6.
>
> 1. 'forrest war' on a seed-sample site.
> 2. Copied WAR file to Jettys /webapp/ directory. (rather than configure
> files)
> 3. java -jar start.jar etc/jetty.xml etc/jetty.xml
> 4. http://localhost:8080/my-project/
>
> All works fine.
>
> So maybe you are using the forrest jetty or some other way of doing it.
> Could you guide me through your scenario so I can try it?
Yes i meant using a full separate version of Jetty, not Forrest's
packaged one which is a cut-down of an old Jetty.
I followed your method today, and yes it works for me
with Java 5 and Jetty 6.
I had been trying with a local configuration and starting
Jetty with a shell-script. Perhaps that config was not correct.
Anyway just using default config and 'java -jar start.jar etc/jetty.xml'
it works.
However doing the same with Java 1.4.2 is not working.
It gives the error described in FOR-765.
> I will test it shortly on a dispatcher site.
How did you go?
-David
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
Ray Mendonsa wrote:
> Ahhh. But then I stumbled upon this thread:
> http://marc.theaimsgroup.com/?l=forrest-dev&m=113448256225368&w=2
Yes, see http://issues.apache.org/jira/browse/FOR-735
Thanks for finding that patch which disappeared in the
mail archive. I linked it to the jira issue.
> So now I know the plugins are deployed in war target only. I confirmed that
> feeder *was* deploying OK if I used war target. In my setup (Forrest cmd
> line on WinXp/Java 1.5.0_06, war running on FC2 Linux/Java 1.5.0_09/Tomcat
> 5.0.30)
Thanks for testing the 'forrest war'.
-David
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ray Mendonsa <ra...@linklord.com>.
Ahhh. But then I stumbled upon this thread:
http://marc.theaimsgroup.com/?l=forrest-dev&m=113448256225368&w=2
So now I know the plugins are deployed in war target only. I confirmed that
feeder *was* deploying OK if I used war target. In my setup (Forrest cmd
line on WinXp/Java 1.5.0_06, war running on FC2 Linux/Java 1.5.0_09/Tomcat
5.0.30)
Thanks,
Ray
-----Original Message-----
From: Ray Mendonsa [mailto:ray@linklord.com]
Sent: Thursday, November 09, 2006 9:56 PM
To: dev@forrest.apache.org
Subject: RE: testing forrest-0.8 as WAR in Jetty and Tomcat
wrt plugin deployment, I did confirm that the feeder plugin was not deployed
for me with the current 0.80-dev code with 'forrest webapp' run under Tomcat
5.0.30 on FC2 Linux under Java 1.5.0_09. Feeder plugin was working OK with
'forrest run'. Note 'forrest webapp' was run on Windows with 1.5.0_06 JDK
for this test.
There's an error reading
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml . There's /build/plugins/ folder in the output of 'forrest
webapp'.
I will look into it myself, but it will take me a while because I'm a
Forrest n00b and don't know the correct behaviors with certainty.
Ray
====
<snip>
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by Ray Mendonsa <ra...@linklord.com>.
wrt plugin deployment, I did confirm that the feeder plugin was not deployed
for me with the current 0.80-dev code with 'forrest webapp' run under Tomcat
5.0.30 on FC2 Linux under Java 1.5.0_09. Feeder plugin was working OK with
'forrest run'. Note 'forrest webapp' was run on Windows with 1.5.0_06 JDK
for this test.
There's an error reading
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml . There's /build/plugins/ folder in the output of 'forrest
webapp'.
I will look into it myself, but it will take me a while because I'm a
Forrest n00b and don't know the correct behaviors with certainty.
Ray
====
ERROR (2006-11-09) 21:32.56:820 [core.modules.mapper.lm] (/)
TP-Processor3/SelectNode: Ignoring locationmap config exception: Unable to
build LocationMap.
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
build LocationMap.
at
org.apache.forrest.locationmap.lm.MountNode.loadConfiguration(MountNode.java
:129)
at
org.apache.forrest.locationmap.lm.MountNode.getLocationMap(MountNode.java:87
)
at
org.apache.forrest.locationmap.lm.MountNode.locate(MountNode.java:157)
at
org.apache.forrest.locationmap.lm.SelectNode.locate(SelectNode.java:110)
at
org.apache.forrest.locationmap.lm.LocatorNode.locate(LocatorNode.java:122)
at
org.apache.forrest.locationmap.lm.LocationMap.locate(LocationMap.java:276)
at
org.apache.forrest.locationmap.lm.MountNode.locate(MountNode.java:157)
at
org.apache.forrest.locationmap.lm.SelectNode.locate(SelectNode.java:110)
at
org.apache.forrest.locationmap.lm.LocatorNode.locate(LocatorNode.java:122)
at
org.apache.forrest.locationmap.lm.LocationMap.locate(LocationMap.java:276)
at
org.apache.forrest.locationmap.LocationMapModule.getAttribute(LocationMapMod
ule.java:181)
at
org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolve
r.processModule(PreparedVariableResolver.java:246)
at
org.apache.cocoon.components.treeprocessor.variables.PreparedVariableResolve
r.resolve(PreparedVariableResolver.java:197)
at
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectN
ode.java:77)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:77)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(Pipel
ineNode.java:155)
at
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invo
keNodes(AbstractParentProcessingNode.java:77)
at
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(Pipe
linesNode.java:95)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:292)
at
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(Con
creteTreeProcessor.java:223)
at
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcess
or.java:289)
at org.apache.cocoon.Cocoon.process(Cocoon.java:557)
at
org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:364)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContext
Valve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118
)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContex
t.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.excalibur.source.SourceNotFoundException:
file:<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/loca
tionmap.xml doesn't exist.
at
org.apache.excalibur.source.impl.FileSource.getInputStream(FileSource.java:1
50)
at
org.apache.forrest.locationmap.lm.MountNode.loadConfiguration(MountNode.java
:125)
... 49 more
Caused by: java.io.FileNotFoundException:
<contextpath>/build/plugins/org.apache.forrest.plugin.input.feeder/locationm
ap.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at
org.apache.excalibur.source.impl.FileSource.getInputStream(FileSource.java:1
46)
... 50 more
Re: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
On Thu, Aug 10, 2006 David Crossley wrote:
>
> Would developers please try to use the current forrest
> trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
>
> Do ...
> cd my-new-directory
> forrest seed-sample war
>
> Then deploy the my-project.war to your servlet container.
>
> Then try it on a site that uses your favourite plugins.
>
> This is needed to progress towards the 0.8 release.
>
> We need reports for various versions of Jetty and Tomcat,
> so we need multiple developers to help with this testing.
Please, pretty please. Reports of success are good too.
We especially need to know that plugin deployment works properly.
The "seed-sample" site only includes the PDF plugin.
It would also be good to hear that Dispatcher works properly
in webapp mode.
If there are any out-of-the-ordinary configuration,
then please say. One of us can make a doc about
deployment issues for various situations.
-David
RE: testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Thursday, 10 August 2006 7:35 AM
> To: dev@forrest.apache.org
> Subject: testing forrest-0.8 as WAR in Jetty and Tomcat
>
> Would developers please try to use the current forrest
> trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
>
> Do ...
> cd my-new-directory
> forrest seed-sample war
>
> Then deploy the my-project.war to your servlet container.
>
> Then try it on a site that uses your favourite plugins.
>
> This is needed to progress towards the 0.8 release.
>
> We need reports for various versions of Jetty and Tomcat,
> so we need multiple developers to help with this testing.
You already have my success story for Tomcat 6. So I thought
I would try using Jetty.
1. - I have downloaded Jetty 6.
2. - java -jar start.jar etc/jetty.xml etc/jetty.xml
3. - Localhost:8080 brings up jetty sample site ok
4. - Download Maven 2
5. - Build Jetty with Maven 2, Build failed error which
I summised to be
http://bugs.sun.com/bugdatabase/view_bug.do;jsessionid=70f6a0e1d75ac913d8b31
fba76c1:YfiG?bug_id=4352234
( 4 and 5, I was going to run 'mvn jetty:run' to use the plugin but this
Didn't work out.)
So in the end, using Full Jetty version 6.
1. 'forrest war' on a seed-sample site.
2. Copied WAR file to Jettys /webapp/ directory. (rather than configure
files)
3. java -jar start.jar etc/jetty.xml etc/jetty.xml
4. http://localhost:8080/my-project/
All works fine.
So maybe you are using the forrest jetty or some other way of doing it.
Could you guide me through your scenario so I can try it?
I will test it shortly on a dispatcher site.
Gav...
testing forrest-0.8 as WAR in Jetty and Tomcat
Posted by David Crossley <cr...@apache.org>.
Would developers please try to use the current forrest
trunk 0.8-dev as a WAR archive in Jetty and Tomcat.
Do ...
cd my-new-directory
forrest seed-sample war
Then deploy the my-project.war to your servlet container.
Then try it on a site that uses your favourite plugins.
This is needed to progress towards the 0.8 release.
We need reports for various versions of Jetty and Tomcat,
so we need multiple developers to help with this testing.
-David
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Gav.... wrote:
> > From: David Crossley
> > >
> > > > ------------------------
> > > > FOR-865 Add missing entries to status.xml to generate the changes list
> > > > http://issues.apache.org/jira/browse/FOR-865
> > > >
> > > > Still need to review ...
> > >
> > > I have done a heap a while ago. Since then i noticed a few
> > > entries being added but more new work needs to be mentioned.
> > >
> > > See "svn log status.xml" for date of last effort and
> > > browse forward in the mailing lists (dev and svn) to
> > > find more that should be mentioned.
I am not saying that i was thorough with that sweep
either. As you know it is difficult.
> > The last entry was for 19/09/2006. I have never updated this file, I will
> > take a look but may miss a few because I need to work out what is regarded
> > as major enough to be here.
>
> Up to the person doing the job to decide. Look at past entries
> for example. Think from the point-of-view of an outside person
> and what they need to be alerted to.
Of course one of the major things is when people have made
contributions, then we should add an entry. This gets them listed
in http://forrest.apache.org/docs_0_80/changes.html#Contributors+to+this+release
and hopefully encourages them some more ;-)
http://forrest.apache.org/guidelines.html#contribution
and the discussion linked to in this FOR-865.
-David
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
Gav.... wrote:
> From: David Crossley
> >
> > > ------------------------
> > > FOR-865 Add missing entries to status.xml to generate the changes list
> > > http://issues.apache.org/jira/browse/FOR-865
> > >
> > > Still need to review ...
> >
> > I have done a heap a while ago. Since then i noticed a few
> > entries being added but more new work needs to be mentioned.
> >
> > See "svn log status.xml" for date of last effort and
> > browse forward in the mailing lists (dev and svn) to
> > find more that should be mentioned.
>
> The last entry was for 19/09/2006. I have never updated this file, I will
> take a look but may miss a few because I need to work out what is regarded
> as major enough to be here.
Up to the person doing the job to decide. Look at past entries
for example. Think from the point-of-view of an outside person
and what they need to be alerted to.
> > > ... and move some out into each plugin.
> >
> > Still needs doing.
>
> So plugin specific changes should not be here at all?
Correct.
> > > Need to ensure each new plugin is mentioned in top-level status file.
> >
> > Still needs doing.
> >
> > > Also need to set the importance attribute for some entries so that
> > > they show up in our release notes.
> >
> > Still needs doing.
> >
> > Patches welcome.
>
> So all entries need to be of a certain importance to warrant being there is
> the first place. From this list then we need to filter out the cream of the
> crop that made the most difference ? What level of importance gets shown up
> in the release notes?
That is described in FOR-865 ... importance=high
See also http://forrest.apache.org/procedures/release/How_to_release.html#prep
which gives the URL for automatically generating an announcement.
This gets hand tweaked to make the real one.
Also, there are notes related to some of the important ones
in /docs_0_80/upgrading_08.html
> > > ------------------------
> > > FOR-765 forrest war and classpath issues with Jetty
> > > http://issues.apache.org/jira/browse/FOR-765
> > >
> > > Same as last time.
> > > Ask again for people to try a WAR archive.
> >
> > Default config seems okay with Jetty 6 and Java 5.
>
> So what do we do here, create/update some docs to say to upgrade to
> latest Java, Latest Jetty (and Tomcat 6??) then close the issue.?
As part of the release process we need to decide the base
Java version. So perhaps this will be a factor. Can anyone
confirm the suitability of Java 1.4?
> > ------------------------
> > FOR-960 PNG Images not transparent in IE6 or below
> > https://issues.apache.org/jira/browse/FOR-960
> >
> > This one is a new addition to the roadmap.
>
> And this has always been an issue really, just not added to Jira until
> recently. I had suggested that using the MS proprietry AlphaImageLoader
> would cure the problem - which it would, but need to do other changes to
> get to that point. I am also thinking there may be another way of doing
> it.
>
> I will see about getting on with this again soon (I had a bit of an attempt
> last week/week before). I don't think it is important enough to keep on
> the 0.8 roadmap and hold up a release so if I don't get it done then we can
> certainly delay until 0.9.
There are many issues that would be "nice to do". Quite some
time ago we started pushing all non-essential issues over
to 0.9-dev. People can still work on those if they want to.
See http://forrest.apache.org/issues.html#filters
FOR-unscheduled and also the 0.9 Jira Road Map.
-David
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
>
> >>------------------------
> >>FOR-635 images not reproduced in PDFs, if sources are in xdocs/images
> >>directory
> >>http://issues.apache.org/jira/browse/FOR-635
> >>
> >>Gavin did some investigation. It is complex.
> >>Suggest delay until 0.9-dev
> >
> >?
>
> I see this as a significant issue, PDF generation is a commonly used
> feature. Whilst it only affects images in xdocs/images and therefore can
> be worked around it's a pretty ugly workaround.
See some comments in the issue. It is sort of connected to
having the main location at resources/images rather than xdocs/images.
Our documentation needs to be clear on that and our seed site
structures need to re-inforce it.
One trouble is that our normal sitemap/locationmap handling
of these has grown to be very complex to support previous
locations.
IIRC the *.fo pipeline leaves it up to a stylesheet to
figure out the image locations, which is no-where near
as powerful as our sitemap/locationmap ability.
> I feel sure it can be sorted out, but haven't looked at it.
>
> I guess that means I volunteer since Gav and yourself have looked over this.
I have not really tried to. Just built the demonstration
of the problems in the seed site samples/linking.html#images
-David
Re: review list of scheduled issues for 0.8 release
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
>> ------------------------
>> FOR-533 Auto Generate plugins.xml entry
>> http://issues.apache.org/jira/browse/FOR-533
>>
>> Same as last time.
>> Ross explained what needs to happen and suggested we do this for 0.8
>
> Recent progress is being made.
I note your comments on this (separate thread), I'll complete this issue
- thanks for the review.
>> ------------------------
>> FOR-742 trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
>> http://issues.apache.org/jira/browse/FOR-742
>>
>> Perhaps this can be closed. Cyriaque and Ross seem happy.
>
> We will probably only be sure after we have done the release.
As far as I can tell it is all done but for ensuring that there is an
unversioned copy of each plugin in the 0.7 release tree. i.e. we copy
the most recent 0.7 versioned plugin to the root of the 0.7 download
with no version number.
I know this is ugly, but that's how the hack works ;-)
We'll move to Ivy deployment of plugins (or Cocoon blocks, if they are
versioned) in 0.9
>> ------------------------
>> FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
>> http://issues.apache.org/jira/browse/FOR-635
>>
>> Gavin did some investigation. It is complex.
>> Suggest delay until 0.9-dev
>
> ?
I see this as a significant issue, PDF generation is a commonly used
feature. Whilst it only affects images in xdocs/images and therefore can
be worked around it's a pretty ugly workaround.
I feel sure it can be sorted out, but haven't looked at it.
I guess that means I volunteer since Gav and yourself have looked over this.
Ross
RE: review list of scheduled issues for 0.8 release
Posted by "Gav...." <br...@brightontown.com.au>.
> -----Original Message-----
> From: David Crossley [mailto:crossley@apache.org]
> Sent: Friday, 23 March 2007 4:24 PM
> To: dev@forrest.apache.org
> Subject: Re: review list of scheduled issues for 0.8 release
>
> What is that rumbling sound? Seems like action towards a release.
> Lets try to catch the train this time.
>
> We need the help of the whole development community.
> There are over 130 of us.
> http://people.apache.org/~coar/mlists.html#forrest.apache.org
>
> You don't need to be a committer to help.
>
> Please review Jira issues and comment, suggest fixes,
> improve vital documentation, and do testing.
>
> The next step is to refine the list of scheduled issues
> one final time. See below.
>
> My next task is to propose a Release Plan to outline the
> procedure and settle on specific dates for each stage.
> Then we will vote on that. Being so explicit is good. It focusses
> attention and encourages people to get involved. It should be
> a fun and rewarding event for all to deliver a good product
> that we can later use.
>
> Anyway, let us now review the issues again.
> When we reach a certain date in the Release Plan,
> any remaining scheduled issues will just get their
> Fix-Version attribute bumped to 0.9-dev
> So let us do what we can until then.
>
> Nov 08, 2006 David Crossley wrote:
> > Wow, another four months have flown by since last time
> > that we tried to narrow down the list of issues.
>
> Wow, again :-)
>
> > All developers can assist with this, don't leave it to
> > the committers. If you want to see the 0.8 release then
> > please help.
>
> ;-) ;-)
>
> > We are down from 37 to 26 issues for filter "FOR-roadmap-dev".
> http://forrest.apache.org/issues.html#filters
> >
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&request
> Id=12310820
>
> With recent efforts that is now down to 15 ... hooray.
>
> > The main reason for the reduction is that last time we decided
> > to delay some issues. A little progress has also been made with
> > some other things.
> >
> > I have added some comments below to explain the status of each.
> > When it is the same as last time, then i tried to summarise
> > previous comments.
> >
> > I have tried to identify some that can be moved over to 0.9-dev.
> >
> > Many issues seem to be the same as last time, even though they
> > only require some simple documentation. Please help.
>
> Recent efforts have helped a lot. Thanks.
>
> > ------------------------
> > FOR-855 verify the license situation prior to each release
> > http://issues.apache.org/jira/browse/FOR-855
> >
> > Because we let the release slip past the cut-off date 1 November,
> > we now need to fully meet the new policy. Main job is to organise
> > the license files for supporting products and refer to them.
> > See Cliff's doc linked from FOR-855.
>
> I will take that one on.
>
> > ------------------------
> > FOR-865 Add missing entries to status.xml to generate the changes list
> > http://issues.apache.org/jira/browse/FOR-865
> >
> > Still need to review ...
>
> I have done a heap a while ago. Since then i noticed a few
> entries being added but more new work needs to be mentioned.
>
> See "svn log status.xml" for date of last effort and
> browse forward in the mailing lists (dev and svn) to
> find more that should be mentioned.
The last entry was for 19/09/2006. I have never updated this file, I will
take a look but may miss a few because I need to work out what is regarded
as major enough to be here.
>
> > ... and move some out into each plugin.
>
> Still needs doing.
So plugin specific changes should not be here at all?
>
> > Need to ensure each new plugin is mentioned in top-level status file.
>
> Still needs doing.
>
> > Also need to set the importance attribute for some entries so that
> > they show up in our release notes.
>
> Still needs doing.
>
> Patches welcome.
So all entries need to be of a certain importance to warrant being there is
the first place. From this list then we need to filter out the cream of the
crop that made the most difference ? What level of importance gets shown up
in the release notes?
>
> > ------------------------
> > FOR-868 add relevant notes to the "Upgrading" xdoc
> > http://issues.apache.org/jira/browse/FOR-868
> >
> > Needs attention.
>
> Some work has been done, but probably needs more.
>
> > ------------------------
> > FOR-533 Auto Generate plugins.xml entry
> > http://issues.apache.org/jira/browse/FOR-533
> >
> > Same as last time.
> > Ross explained what needs to happen and suggested we do this for 0.8
>
> Recent progress is being made.
>
> > ------------------------
> > FOR-639 define terminology for the various aspects of Dispatcher
> > http://issues.apache.org/jira/browse/FOR-639
> >
> > Same as last time.
> > A doc has been started. We need more content.
>
> This one was taken off the roadmap. However,
> it would be great if this was done because it will
> save a lot of confusion on the mailing list, because
> people are sure to be using it.
I have done some more work on this. It is possible that it is more
or less complete, but needs others to take a look to make sure what
I have put there is accurate and if there is anything else that can
go there.
As a side-effect of doing this I also updated two of the three howTo's
to reflect current practice, these really do need checking for accuracy,
but hope I got it right :)
>
> > ------------------------
> > FOR-735 Plugins are not correctly deployed in webapp mode
> > http://issues.apache.org/jira/browse/FOR-735
> >
> > Same as last time.
> > Investigate.
> > Johannes and others provided suggestions in Jira and the mailing list.
> > Perhaps we just need a document to describe how to use Forrest as a web
> application.
>
> There is a patch provided. Can someone investigate.
>
> > ------------------------
> > FOR-742 trouble accessing unversioned plugin for a released version of
> Forrest, e.g. projectInfo
> > http://issues.apache.org/jira/browse/FOR-742
> >
> > Perhaps this can be closed. Cyriaque and Ross seem happy.
>
> We will probably only be sure after we have done the release.
>
> > ------------------------
> > FOR-241 character entities (e.g. ampersand) are expanded again for href
> or src attributes
> > http://issues.apache.org/jira/browse/FOR-241
> >
> > Suggest delay until 0.9 as the issue has been around for a long time.
>
> Ditto.
>
> > ------------------------
> > FOR-765 forrest war and classpath issues with Jetty
> > http://issues.apache.org/jira/browse/FOR-765
> >
> > Same as last time.
> > Ask again for people to try a WAR archive.
>
> Default config seems okay with Jetty 6 and Java 5.
So what do we do here, create/update some docs to say to upgrade to
latest Java, Latest Jetty (and Tomcat 6??) then close the issue.?
>
> > ------------------------
> > FOR-911 decide content of release
> > http://issues.apache.org/jira/browse/FOR-911
> >
> > Need to investigate the linked mails and make a Proposal.
>
> I will work on that one after getting the Release Plan done.
>
> Will probably be similar size and packaging to
> last time, sorry. Next release we hope to use Ivy.
>
> > ------------------------
> > FOR-922 update all docs that explain sitemap fragments
> > http://issues.apache.org/jira/browse/FOR-922
> >
> > Reasonably simple documentation job. Find all docs that give sitemap
> examples
> > and ensure that they are current.
>
> We have a "warning" workaround. However there is still
> time before the release for someone to patch these docs.
>
> > ------------------------
> > FOR-731 empty linkmap.html document, side-effect of workaround to FOR-
> 675
> > http://issues.apache.org/jira/browse/FOR-731
> >
> > Same as last time.
> > Investigate.
>
> As Gav suggests, move to 0.9-dev.
Have moved it to 0.9.
>
> > ------------------------
> > FOR-861 Update locationmap docs for working with remote files
> > http://issues.apache.org/jira/browse/FOR-861
> >
> > Same as last time.
> > Should be a simple documentation job. Ross provides the references.
>
> Anyone can help.
>
> > ------------------------
> > FOR-644 code-style cleanup for xml files
> > http://issues.apache.org/jira/browse/FOR-644
> >
> > This should be able to be done just prior to release.
> > We had delayed this, but i reckon that it is worth trying.
>
> I will attempt it straight after the code freeze starts.
>
> Need to work out an Ant target for a postfix to re-insert the
> removed space after inline closing tags (or maybe Tidy is fixed).
> Recently i noticed Cyriaque using a regexp replacement task,
> perhaps that will work for this.
>
> Everyone please get your changes contributed before that.
> Includes xml docs, configuration files, sitemaps, XSLs, etc.
>
> > ------------------------
> > FOR-635 images not reproduced in PDFs, if sources are in xdocs/images
> directory
> > http://issues.apache.org/jira/browse/FOR-635
> >
> > Gavin did some investigation. It is complex.
> > Suggest delay until 0.9-dev
>
> ?
Right now I'm out of puff on this issue, if someone else can pick it up
and sort it before the code freeze starts then great, otherwise I don't
think I will be able to take another look until after the release, as part
of the 0.9 roadmap.
>
> ------------------------
> FOR-960 PNG Images not transparent in IE6 or below
> https://issues.apache.org/jira/browse/FOR-960
>
> This one is a new addition to the roadmap.
And this has always been an issue really, just not added to Jira until
recently. I had suggested that using the MS proprietry AlphaImageLoader
would cure the problem - which it would, but need to do other changes to
get to that point. I am also thinking there may be another way of doing
it.
I will see about getting on with this again soon (I had a bit of an attempt
last week/week before). I don't think it is important enough to keep on
the 0.8 roadmap and hold up a release so if I don't get it done then we can
certainly delay until 0.9.
Gav...
>
> -David
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.446 / Virus Database: 268.18.17/730 - Release Date: 3/22/2007
> 7:44 AM
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
What is that rumbling sound? Seems like action towards a release.
Lets try to catch the train this time.
We need the help of the whole development community.
There are over 130 of us.
http://people.apache.org/~coar/mlists.html#forrest.apache.org
You don't need to be a committer to help.
Please review Jira issues and comment, suggest fixes,
improve vital documentation, and do testing.
The next step is to refine the list of scheduled issues
one final time. See below.
My next task is to propose a Release Plan to outline the
procedure and settle on specific dates for each stage.
Then we will vote on that. Being so explicit is good. It focusses
attention and encourages people to get involved. It should be
a fun and rewarding event for all to deliver a good product
that we can later use.
Anyway, let us now review the issues again.
When we reach a certain date in the Release Plan,
any remaining scheduled issues will just get their
Fix-Version attribute bumped to 0.9-dev
So let us do what we can until then.
Nov 08, 2006 David Crossley wrote:
> Wow, another four months have flown by since last time
> that we tried to narrow down the list of issues.
Wow, again :-)
> All developers can assist with this, don't leave it to
> the committers. If you want to see the 0.8 release then
> please help.
;-) ;-)
> We are down from 37 to 26 issues for filter "FOR-roadmap-dev".
http://forrest.apache.org/issues.html#filters
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310820
With recent efforts that is now down to 15 ... hooray.
> The main reason for the reduction is that last time we decided
> to delay some issues. A little progress has also been made with
> some other things.
>
> I have added some comments below to explain the status of each.
> When it is the same as last time, then i tried to summarise
> previous comments.
>
> I have tried to identify some that can be moved over to 0.9-dev.
>
> Many issues seem to be the same as last time, even though they
> only require some simple documentation. Please help.
Recent efforts have helped a lot. Thanks.
> ------------------------
> FOR-855 verify the license situation prior to each release
> http://issues.apache.org/jira/browse/FOR-855
>
> Because we let the release slip past the cut-off date 1 November,
> we now need to fully meet the new policy. Main job is to organise
> the license files for supporting products and refer to them.
> See Cliff's doc linked from FOR-855.
I will take that one on.
> ------------------------
> FOR-865 Add missing entries to status.xml to generate the changes list
> http://issues.apache.org/jira/browse/FOR-865
>
> Still need to review ...
I have done a heap a while ago. Since then i noticed a few
entries being added but more new work needs to be mentioned.
See "svn log status.xml" for date of last effort and
browse forward in the mailing lists (dev and svn) to
find more that should be mentioned.
> ... and move some out into each plugin.
Still needs doing.
> Need to ensure each new plugin is mentioned in top-level status file.
Still needs doing.
> Also need to set the importance attribute for some entries so that
> they show up in our release notes.
Still needs doing.
Patches welcome.
> ------------------------
> FOR-868 add relevant notes to the "Upgrading" xdoc
> http://issues.apache.org/jira/browse/FOR-868
>
> Needs attention.
Some work has been done, but probably needs more.
> ------------------------
> FOR-533 Auto Generate plugins.xml entry
> http://issues.apache.org/jira/browse/FOR-533
>
> Same as last time.
> Ross explained what needs to happen and suggested we do this for 0.8
Recent progress is being made.
> ------------------------
> FOR-639 define terminology for the various aspects of Dispatcher
> http://issues.apache.org/jira/browse/FOR-639
>
> Same as last time.
> A doc has been started. We need more content.
This one was taken off the roadmap. However,
it would be great if this was done because it will
save a lot of confusion on the mailing list, because
people are sure to be using it.
> ------------------------
> FOR-735 Plugins are not correctly deployed in webapp mode
> http://issues.apache.org/jira/browse/FOR-735
>
> Same as last time.
> Investigate.
> Johannes and others provided suggestions in Jira and the mailing list.
> Perhaps we just need a document to describe how to use Forrest as a web application.
There is a patch provided. Can someone investigate.
> ------------------------
> FOR-742 trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
> http://issues.apache.org/jira/browse/FOR-742
>
> Perhaps this can be closed. Cyriaque and Ross seem happy.
We will probably only be sure after we have done the release.
> ------------------------
> FOR-241 character entities (e.g. ampersand) are expanded again for href or src attributes
> http://issues.apache.org/jira/browse/FOR-241
>
> Suggest delay until 0.9 as the issue has been around for a long time.
Ditto.
> ------------------------
> FOR-765 forrest war and classpath issues with Jetty
> http://issues.apache.org/jira/browse/FOR-765
>
> Same as last time.
> Ask again for people to try a WAR archive.
Default config seems okay with Jetty 6 and Java 5.
> ------------------------
> FOR-911 decide content of release
> http://issues.apache.org/jira/browse/FOR-911
>
> Need to investigate the linked mails and make a Proposal.
I will work on that one after getting the Release Plan done.
Will probably be similar size and packaging to
last time, sorry. Next release we hope to use Ivy.
> ------------------------
> FOR-922 update all docs that explain sitemap fragments
> http://issues.apache.org/jira/browse/FOR-922
>
> Reasonably simple documentation job. Find all docs that give sitemap examples
> and ensure that they are current.
We have a "warning" workaround. However there is still
time before the release for someone to patch these docs.
> ------------------------
> FOR-731 empty linkmap.html document, side-effect of workaround to FOR-675
> http://issues.apache.org/jira/browse/FOR-731
>
> Same as last time.
> Investigate.
As Gav suggests, move to 0.9-dev.
> ------------------------
> FOR-861 Update locationmap docs for working with remote files
> http://issues.apache.org/jira/browse/FOR-861
>
> Same as last time.
> Should be a simple documentation job. Ross provides the references.
Anyone can help.
> ------------------------
> FOR-644 code-style cleanup for xml files
> http://issues.apache.org/jira/browse/FOR-644
>
> This should be able to be done just prior to release.
> We had delayed this, but i reckon that it is worth trying.
I will attempt it straight after the code freeze starts.
Need to work out an Ant target for a postfix to re-insert the
removed space after inline closing tags (or maybe Tidy is fixed).
Recently i noticed Cyriaque using a regexp replacement task,
perhaps that will work for this.
Everyone please get your changes contributed before that.
Includes xml docs, configuration files, sitemaps, XSLs, etc.
> ------------------------
> FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
> http://issues.apache.org/jira/browse/FOR-635
>
> Gavin did some investigation. It is complex.
> Suggest delay until 0.9-dev
?
------------------------
FOR-960 PNG Images not transparent in IE6 or below
https://issues.apache.org/jira/browse/FOR-960
This one is a new addition to the roadmap.
-David
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
Wow, another four months have flown by since last time
that we tried to narrow down the list of issues.
All developers can assist with this, don't leave it to
the committers. If you want to see the 0.8 release then
please help.
We are down from 37 to 26 issues for filter "FOR-roadmap-dev".
http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310820
The main reason for the reduction is that last time we decided
to delay some issues. A little progress has also been made with
some other things.
I have added some comments below to explain the status of each.
When it is the same as last time, then i tried to summarise
previous comments.
I have tried to identify some that can be moved over to 0.9-dev.
Many issues seem to be the same as last time, even though they
only require some simple documentation. Please help.
------------------------
FOR-855 verify the license situation prior to each release
http://issues.apache.org/jira/browse/FOR-855
Because we let the release slip past the cut-off date 1 November,
we now need to fully meet the new policy. Main job is to organise
the license files for supporting products and refer to them.
See Cliff's doc linked from FOR-855.
------------------------
FOR-865 Add missing entries to status.xml to generate the changes list
http://issues.apache.org/jira/browse/FOR-865
Still need to review and move some out into each plugin.
Need to ensure each new plugin is mentioned in top-level status file.
Also need to set the importance attribute for some entries so that
they show up in our release notes.
------------------------
FOR-868 add relevant notes to the "Upgrading" xdoc
http://issues.apache.org/jira/browse/FOR-868
Needs attention.
------------------------
FOR-533 Auto Generate plugins.xml entry
http://issues.apache.org/jira/browse/FOR-533
Same as last time.
Ross explained what needs to happen and suggested we do this for 0.8
------------------------
FOR-639 define terminology for the various aspects of Dispatcher
http://issues.apache.org/jira/browse/FOR-639
Same as last time.
A doc has been started. We need more content.
------------------------
FOR-735 Plugins are not correctly deployed in webapp mode
http://issues.apache.org/jira/browse/FOR-735
Same as last time.
Investigate.
Johannes and others provided suggestions in Jira and the mailing list.
Perhaps we just need a document to describe how to use Forrest as a web application.
------------------------
FOR-711 Cache results from the Locationmap
http://issues.apache.org/jira/browse/FOR-711
Same as last time.
Needs FAQ and get some comments from mail archives into docs.
------------------------
FOR-742 trouble accessing unversioned plugin for a released version of Forrest, e.g. projectInfo
http://issues.apache.org/jira/browse/FOR-742
Perhaps this can be closed. Cyriaque and Ross seem happy.
------------------------
FOR-241 character entities (e.g. ampersand) are expanded again for href or src attributes
http://issues.apache.org/jira/browse/FOR-241
Suggest delay until 0.9 as the issue has been around for a long time.
------------------------
FOR-200 Locationmap for Forrest and Users
http://issues.apache.org/jira/browse/FOR-200
Same as last time.
This must be getting close. Investigate.
------------------------
FOR-546 Sitemap reference doc should be updated to reflect plugin architecture
http://issues.apache.org/jira/browse/FOR-546
Same as last time.
Needs to be done.
------------------------
FOR-666 clarify the sitemap matches etc. in FAQ about non-skinned html
http://issues.apache.org/jira/browse/FOR-666
Delay until 0.9-dev.
------------------------
FOR-726 use locationmap in all of the plugins
http://issues.apache.org/jira/browse/FOR-726
Same as last time.
This must be getting close. Investigate.
------------------------
FOR-765 forrest war gets NoSuchMethodError for some core transformer
http://issues.apache.org/jira/browse/FOR-765
Same as last time.
Ask again for people to try a WAR archive.
------------------------
FOR-776 rationalise the pluginTemplate and current plugins to have minimal configuration files, etc.
http://issues.apache.org/jira/browse/FOR-776
Delayed to 0.9-dev
------------------------
FOR-901 Review the note on the home page about first forrest run and retrieving plugins from network
http://issues.apache.org/jira/browse/FOR-901
Same as last time.
Should be simple to test this and then fix the home page documentation.
------------------------
FOR-906 locationmap documentation explain this-to-that.xsl naming convention and default lm matches
http://issues.apache.org/jira/browse/FOR-906
Someone needs to do it.
------------------------
FOR-911 decide content of release
http://issues.apache.org/jira/browse/FOR-911
Need to investigate the linked mails and make a Proposal.
------------------------
FOR-922 update all docs that explain sitemap fragments
http://issues.apache.org/jira/browse/FOR-922
Reasonably simple documentation job. Find all docs that give sitemap examples
and ensure that they are current.
------------------------
FOR-936 Forrest "looses" the locale when switching pages
http://issues.apache.org/jira/browse/FOR-936
New issue.
------------------------
FOR-537 Plugin documentation sitemap references
http://issues.apache.org/jira/browse/FOR-537
Same as last time.
Need to explain using plugins in-place and change the refs to sitemap.xmap
into an example for a specific type of plugin, e.g. refer to the input.xmap
instead of sitemap.xmap file.
------------------------
FOR-671 Layering error of HTML headings breaks rest of the page w/o warning
http://issues.apache.org/jira/browse/FOR-671
Same as last time.
Document as FAQ.
------------------------
FOR-731 empty linkmap.html document, side-effect of workaround to FOR-675
http://issues.apache.org/jira/browse/FOR-731
Same as last time.
Investigate.
------------------------
FOR-767 Forrestbot webapp reports succesful even when there are broken links
http://issues.apache.org/jira/browse/FOR-767
There has been some Jira activity, but not yet resolved.
------------------------
FOR-861 Update locationmap docs for working with remote files
http://issues.apache.org/jira/browse/FOR-861
Same as last time.
Should be a simple documentation job. Ross provides the references.
------------------------
FOR-635 images not reproduced in PDFs, if sources are in xdocs/images directory
http://issues.apache.org/jira/browse/FOR-635
Gavin did some investigation. It is complex.
Suggest delay until 0.9-dev
------------------------
FOR-644 code-style cleanup for xml files
http://issues.apache.org/jira/browse/FOR-644
This should be able to be done just prior to release.
We had delayed this, but i reckon that it is worth trying.
------------------------
Re: review list of scheduled issues for 0.8 release
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
>
>>David Crossley wrote:
>>
>>>------------------------
>>>FOR-560 Remove duplicate jars from eclipse plugins
>>>http://issues.apache.org/jira/browse/FOR-560
>>>
>>>Delay until 0.9-dev.
>>
>>Shouldn't even be in a roadmap since this is not part of core.
>
>
> It adds more fat to our release download. I suppose
> that is why it was added to the roadmap.
Lets not include it in the release.
Ross
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> David Crossley wrote:
>
> >------------------------
> >FOR-639 define terminology for the various aspects of Dispatcher
> >http://issues.apache.org/jira/browse/FOR-639
> >
> >A doc has been started by Gavin. We need more content.
>
> Dispatcher is not core, it's not even out of the whiteboard yet.
>
> I'd rather see the dispatcher docs go into the plugins. This was
> proposed recently and nobody objected, but nobody did it either.
Ah, thanks. The original idea was to have a top-level glossary
for general Forrest terms, then specific plugin-specific glossaries.
> >------------------------
> >FOR-546 Sitemap reference doc should be updated to reflect plugin
> >architecture
> >http://issues.apache.org/jira/browse/FOR-546
> >
> >Delay until 0.9-dev.
>
> -1 the 0.8 docs should reflect the 0.8 code.
Okay. Calling all doc writers.
We also need a run through all docs to ensure such.
Need an Issue for that.
> >------------------------
> >FOR-560 Remove duplicate jars from eclipse plugins
> >http://issues.apache.org/jira/browse/FOR-560
> >
> >Delay until 0.9-dev.
>
> Shouldn't even be in a roadmap since this is not part of core.
It adds more fat to our release download. I suppose
that is why it was added to the roadmap.
> >------------------------
> >FOR-767 Forrestbot webapp reports succesful even when there are broken
> >links
> >http://issues.apache.org/jira/browse/FOR-767
> >
> >Investigate.
>
> 0.9-dev not part of core
I thought it was worth someone doing a quick investigation
so left it there until the next round of roadmap tuning.
-David
Re: review list of scheduled issues for 0.8 release
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> ------------------------
> FOR-639 define terminology for the various aspects of Dispatcher
> http://issues.apache.org/jira/browse/FOR-639
>
> A doc has been started by Gavin. We need more content.
Dispatcher is not core, it's not even out of the whiteboard yet.
I'd rather see the dispatcher docs go into the plugins. This was
proposed recently and nobody objected, but nobody did it either.
> ------------------------
> FOR-546 Sitemap reference doc should be updated to reflect plugin architecture
> http://issues.apache.org/jira/browse/FOR-546
>
> Delay until 0.9-dev.
-1 the 0.8 docs should reflect the 0.8 code.
> ------------------------
> FOR-560 Remove duplicate jars from eclipse plugins
> http://issues.apache.org/jira/browse/FOR-560
>
> Delay until 0.9-dev.
Shouldn't even be in a roadmap since this is not part of core.
> ------------------------
> FOR-767 Forrestbot webapp reports succesful even when there are broken links
> http://issues.apache.org/jira/browse/FOR-767
>
> Investigate.
0.9-dev not part of core
Ross
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> David Crossley wrote:
> >
> > ------------------------
> > FOR-868 add relevant notes to the "Upgrading" xdoc
> > http://issues.apache.org/jira/browse/FOR-868
>
> Other people, meaning any developer, could help with this one.
> If you currently have a site using forrest-0.7 then please
> copy it and try with 0.8-dev instead. You should be able to
> just do 'forrest clean; forrest run' with no changes.
Please. Reports of success are just as good.
-David
> I upgraded one recently and found a problem if using an
> own skin rather than the default. Needed to rename the
> skin's xslt/html/*.xsl files to the naming convention
> tab-to-menu.xsl etc.
>
> http://forrest.apache.org/docs/dev/upgrading_08.html
>
> -David
Re: review list of scheduled issues for 0.8 release
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
>
> ------------------------
> FOR-868 add relevant notes to the "Upgrading" xdoc
> http://issues.apache.org/jira/browse/FOR-868
Other people, meaning any developer, could help with this one.
If you currently have a site using forrest-0.7 then please
copy it and try with 0.8-dev instead. You should be able to
just do 'forrest clean; forrest run' with no changes.
I upgraded one recently and found a problem if using an
own skin rather than the default. Needed to rename the
skin's xslt/html/*.xsl files to the naming convention
tab-to-menu.xsl etc.
http://forrest.apache.org/docs/dev/upgrading_08.html
-David
Re: Fixing FOR-533 (was RE: review list of scheduled issues for 0.8
release)
Posted by Ross Gardler <rg...@apache.org>.
Gav.... wrote:
>>------------------------
>>FOR-533 Auto Generate plugins.xml entry
>>http://issues.apache.org/jira/browse/FOR-533
>>
>>Last time Ross said:
>>
>>>This should stay in 0.8, it's a fairly minor job, I've done most of the
>>>preparatory work (I think).
>>
>
> I have looked at this issue and the commits so far, can you explain what is
> Left to do on this so I can have a go.
First, a disclaimer... take a careful note of the "(I think)" at then
end of my comment above and bear in mind that this issue was put forward
for moving to 0.9. If there is more work in it than I estimate then
consider moving it.
Second, another disclaimer... I'm really tired right now so what I type
below may not be 100% accurate. Hopefully it will be enough to get you
started.
I've done some work to define all the information that is needed in each
plugins entry of plugins.xml within the build.xml file of that plugin.
There may be a field or two missing, but they can be added very easily.
We then need to create an XSL that will generate the plugins.xml entry
for that plugin.
Next we need to use that XSL to create the complete plugins.xml file by
looking up all the build.xml files in the defined plugins directory.
There is no need to write the generated plugins.xml file to disk (other
than to the SVN temp workspace when deploying), however, this will be
the first easy hack to do. This would be a hack because we will be
writing to the Forrest source tree with the build files - a definite
nono, but it will allow testing.
Once this is working we will need to reuse the plugins.xml generating
XSL in the core sitemp so that when we request plugins.xml, in order to
generate the plugins index page, it will dynamically generate it from
the available plugins.
(I have a feeling I am missing something important in this last paragraph)
Ross
Fixing FOR-533 (was RE: review list of scheduled issues for 0.8 release)
Posted by "Gav...." <br...@brightontown.com.au>.
> ------------------------
> FOR-533 Auto Generate plugins.xml entry
> http://issues.apache.org/jira/browse/FOR-533
>
> Last time Ross said:
> > This should stay in 0.8, it's a fairly minor job, I've done most of the
> > preparatory work (I think).
>
I have looked at this issue and the commits so far, can you explain what is
Left to do on this so I can have a go.
Gav...