Plugin documentation review status
Copied below is the output of a build check for each plugin's documentation content, checked against r1054170. This is likely lower priority than general release preparations, but a status overview nonetheless. Does automatic testing of plugin documentation already take place somewhere? If not, I'm a willing volunteer to set something up. org.apache.forrest.plugin.Database: BUILD FAILED org.apache.forrest.plugin.input.baetle: BUILD SUCCESSFUL org.apache.forrest.plugin.input.Blog: BUILD FAILED org.apache.forrest.plugin.input.citations: BUILD SUCCESSFUL org.apache.forrest.plugin.input.Daisy: (build hangs) org.apache.forrest.plugin.input.doac: BUILD SUCCESSFUL org.apache.forrest.plugin.input.doap: BUILD FAILED org.apache.forrest.plugin.input.dtdx: BUILD SUCCESSFUL org.apache.forrest.plugin.input.ecs: BUILD FAILED org.apache.forrest.plugin.input.excel: BUILD SUCCESSFUL org.apache.forrest.plugin.input.feeder: (build hangs) org.apache.forrest.plugin.input.foaf: BUILD FAILED org.apache.forrest.plugin.input.glossary: BUILD SUCCESSFUL org.apache.forrest.plugin.input.Lenya: BUILD FAILED org.apache.forrest.plugin.input.listLocations: BUILD SUCCESSFUL org.apache.forrest.plugin.input.logs: BUILD SUCCESSFUL org.apache.forrest.plugin.input.odt: BUILD SUCCESSFUL org.apache.forrest.plugin.input.OpenOffice.org: BUILD SUCCESSFUL org.apache.forrest.plugin.input.PhotoGallery: (can't build on OpenJDK 6) org.apache.forrest.plugin.input.projectInfo: BUILD FAILED org.apache.forrest.plugin.input.Resume: BUILD FAILED org.apache.forrest.plugin.input.serverStatus: BUILD SUCCESSFUL org.apache.forrest.plugin.input.simplifiedDocbook: BUILD SUCCESSFUL org.apache.forrest.plugin.input.skos: BUILD FAILED org.apache.forrest.plugin.input.tei: BUILD FAILED org.apache.forrest.plugin.input.wiki: BUILD SUCCESSFUL org.apache.forrest.plugin.input.XDoc: BUILD FAILED org.apache.forrest.plugin.internal.DevTools: BUILD FAILED org.apache.forrest.plugin.internal.dispatcher: BUILD FAILED org.apache.forrest.plugin.internal.GoogleSitemap: BUILD FAILED org.apache.forrest.plugin.internal.IMSManifest: BUILD FAILED org.apache.forrest.plugin.internal.NoteTaking: BUILD FAILED org.apache.forrest.plugin.internal.xhtml2: BUILD FAILED org.apache.forrest.plugin.OpenOffice.org-output: BUILD FAILED org.apache.forrest.plugin.output.Anakia: BUILD SUCCESSFUL org.apache.forrest.plugin.output.Chart: BUILD SUCCESSFUL org.apache.forrest.plugin.output.htmlArea: BUILD SUCCESSFUL org.apache.forrest.plugin.output.iCal: BUILD FAILED org.apache.forrest.plugin.output.Markdown: BUILD SUCCESSFUL org.apache.forrest.plugin.output.OOo: BUILD FAILED org.apache.forrest.plugin.output.pdf: BUILD SUCCESSFUL org.apache.forrest.plugin.output.POD: BUILD SUCCESSFUL org.apache.forrest.plugin.output.solr: BUILD FAILED org.apache.forrest.plugin.output.tei: BUILD FAILED org.apache.forrest.plugin.output.Text: BUILD SUCCESSFUL org.apache.forrest.plugin.output.voice: BUILD FAILED rtf-output: BUILD FAILED
[jira] Created: (FOR-1212) Building documentation creates spurious directory tree in project.xdocs-dir/images
Building documentation creates spurious directory tree in project.xdocs-dir/images -- Key: FOR-1212 URL: https://issues.apache.org/jira/browse/FOR-1212 Project: Forrest Issue Type: Bug Components: Plugin: input.PhotoGallery Affects Versions: 0.9-dev Reporter: Brian M Dube Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 6, files are written to: $GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallerysrc/documentation/content/xdocs/images/gallery/demo The full path to $FORREST_HOME is expanded, that is, in the above example insert the full /path/to/forrest/ where it says $FORREST_HOME. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-1212) Building documentation creates spurious directory tree in project.xdocs-dir/images
[ https://issues.apache.org/jira/browse/FOR-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian M Dube updated FOR-1212: -- Description: Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 6, files are written to: $GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/src/documentation/content/xdocs/images/gallery/demo The full path to $FORREST_HOME is expanded, that is, in the above example insert the full /path/to/forrest/ where it says $FORREST_HOME. was: Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 6, files are written to: $GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallerysrc/documentation/content/xdocs/images/gallery/demo The full path to $FORREST_HOME is expanded, that is, in the above example insert the full /path/to/forrest/ where it says $FORREST_HOME. Building documentation creates spurious directory tree in project.xdocs-dir/images -- Key: FOR-1212 URL: https://issues.apache.org/jira/browse/FOR-1212 Project: Forrest Issue Type: Bug Components: Plugin: input.PhotoGallery Affects Versions: 0.9-dev Reporter: Brian M Dube Building the input.PhotoGallery plugin documentation on Ubuntu with Oracle Java 6, files are written to: $GALLERY_PLUGIN/src/documentation/content/xdocs/images/$FORREST_HOME/plugins/org.apache.forrest.plugin.input.PhotoGallery/src/documentation/content/xdocs/images/gallery/demo The full path to $FORREST_HOME is expanded, that is, in the above example insert the full /path/to/forrest/ where it says $FORREST_HOME. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Plugin documentation review status
Brian M Dube wrote: Copied below is the output of a build check for each plugin's documentation content, checked against r1054170. This is likely lower priority than general release preparations, but a status overview nonetheless. Great work. Very necessary. Does automatic testing of plugin documentation already take place somewhere? If not, I'm a willing volunteer to set something up. Not yet. Something that we have wondered about doing. That would be good. We have the forrest zones server, so we can add anything there. Using actual forrestbot might be overkill. See forrest.a.o/zone.html and $SVN/forrest/zone/README.html We already do have some extra test-type targets in our build file. They are used by Gump to do various testing using the newest version (or specific if we need it) of our supporting products. See forrest.a.o/gump.html The ASF buildbot instance also already does one job for us. So there are various things to follow, or invent something new. Have fun. -David
