[jira] Commented: (FOR-517) create test issue
[ http://issues.apache.org/jira/browse/FOR-517?page=comments#action_12312600 ] David Crossley commented on FOR-517: test comment create test issue - Key: FOR-517 URL: http://issues.apache.org/jira/browse/FOR-517 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7-dev Reporter: David Crossley foo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-517) create test issue
create test issue - Key: FOR-517 URL: http://issues.apache.org/jira/browse/FOR-517 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7-dev Reporter: David Crossley foo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-517) create test issue
[ http://issues.apache.org/jira/browse/FOR-517?page=all ] David Crossley resolved FOR-517: Resolution: Fixed it works create test issue - Key: FOR-517 URL: http://issues.apache.org/jira/browse/FOR-517 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7-dev Reporter: David Crossley foo -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-510) Setting Environment Variables Information
[ http://issues.apache.org/jira/browse/FOR-510?page=comments#action_12312705 ] David Crossley commented on FOR-510: No need for special instructions for Mac OS X (== UNIX) unless you are meaning the old Mac OS. Setting Environment Variables Information - Key: FOR-510 URL: http://issues.apache.org/jira/browse/FOR-510 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7-dev Reporter: Addison Berry Priority: Minor Since we describe how to set the Forrest env variables in our docs we should make sure we have instructions for varying OS and versions. If you know of an OS that sets variables differently than that listed in our current docs, please add it in the comments. Make sure you state the OS and version as well as the full process to set the Forrest variables. Current instructions (0.7) In Unix/Linux: change directory to the top-level of the forrest distribution and do ~/apache-forrest-0.7$ export FORREST_HOME=`pwd` ~/apache-forrest-0.7$ export PATH=$PATH:$FORREST_HOME/bin In Windows: Go to My Computer, Properties, Advanced, Environment Variables and add: FORREST_HOME as C:\full\path\to\apache-forrest-0.7 PATH as %PATH%;%FORREST_HOME%\bin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (FOR-465) Logging Error: Writing event to closed stream.
[ http://issues.apache.org/jira/browse/FOR-465?page=all ] David Crossley reopened FOR-465: Assign To: (was: David Crossley) You must be confused. This message still exists. Logging Error: Writing event to closed stream. -- Key: FOR-465 URL: http://issues.apache.org/jira/browse/FOR-465 Project: Forrest Type: Bug Components: Launch 'forrest' Versions: 0.7-dev Reporter: David Crossley Priority: Minor Fix For: 0.7-dev After doing 'forrest' there is a strange error message at the end of Cocoon's run: Logging Error: Writing event to closed stream. This happens on every different project that i have tried. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-514) Do not limit status.xml contexts in project info plugin
[
http://issues.apache.org/jira/browse/FOR-514?page=comments#action_12312710 ]
David Crossley commented on FOR-514:
(Bringing over a comment and a patch from Cyriaque Dupoirieux which were added
during the move of our Jira.)
- Udpate of the Status DTD 1.3 in order to be able to add the following
information :
actionContexts
context id=code title=Changes to the Code Base/
context id=docs title=Changes to the Documentation/
!-- ... --
/actionContexts
- Update of changes2document.xsl in order to take into account the context
title or by default the context ID.
- Update of status.xml files (with documentation associated in comments)
Do not limit status.xml contexts in project info plugin
---
Key: FOR-514
URL: http://issues.apache.org/jira/browse/FOR-514
Project: Forrest
Type: Improvement
Components: Plugin: projectInfo
Reporter: Ross Gardler
Priority: Minor
(This comment brought over from FOR-487)
This improvement of changes page is nice.
I have my own version based on xsl:key definition in order to be able to
simply manage as many contexts as you can define (My Dtd is not limited to
build|docs|code|admin|design.
The advantage - on my opinion - is that my own contexts are very various and
not developpement oriented nor language dependant.
here a short example - using releaseNote... :
http://cyriaque.dupoirieux.free.fr/changes_6.2.1.html
The following code replace the 5 blocks xsl:if test=[EMAIL
PROTECTED]'build'] :
titleVersion xsl:value-of select=@version/ (xsl:value-of
select=@date/)/title
+ xsl:for-each
select=action[generate-id()=generate-id(key('contextes',concat(../@version,
'_', @context)))]
+ xsl:sort select=@context/
+ section
+ titlexsl:value-of select=@context//title
+ ul
+ xsl:apply-templates select=key('contextes',concat(../@version, '_',
@context) )
+ xsl:sort select=@type/
+ /xsl:apply-templates
+ /ul
+ /section
+ /xsl:for-each
Hope you'll like the idea...
Regards,
Cyriaque,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-514) Do not limit status.xml contexts in project info plugin
[ http://issues.apache.org/jira/browse/FOR-514?page=all ]
David Crossley updated FOR-514:
---
Attachment: 514-patch.txt
Do not limit status.xml contexts in project info plugin
---
Key: FOR-514
URL: http://issues.apache.org/jira/browse/FOR-514
Project: Forrest
Type: Improvement
Components: Plugin: projectInfo
Reporter: Ross Gardler
Priority: Minor
Attachments: 514-patch.txt
(This comment brought over from FOR-487)
This improvement of changes page is nice.
I have my own version based on xsl:key definition in order to be able to
simply manage as many contexts as you can define (My Dtd is not limited to
build|docs|code|admin|design.
The advantage - on my opinion - is that my own contexts are very various and
not developpement oriented nor language dependant.
here a short example - using releaseNote... :
http://cyriaque.dupoirieux.free.fr/changes_6.2.1.html
The following code replace the 5 blocks xsl:if test=[EMAIL
PROTECTED]'build'] :
titleVersion xsl:value-of select=@version/ (xsl:value-of
select=@date/)/title
+ xsl:for-each
select=action[generate-id()=generate-id(key('contextes',concat(../@version,
'_', @context)))]
+ xsl:sort select=@context/
+ section
+ titlexsl:value-of select=@context//title
+ ul
+ xsl:apply-templates select=key('contextes',concat(../@version, '_',
@context) )
+ xsl:sort select=@type/
+ /xsl:apply-templates
+ /ul
+ /section
+ /xsl:for-each
Hope you'll like the idea...
Regards,
Cyriaque,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-364) Add Ctrl-C-Info to Jetty Startup-Messages
[ http://issues.apache.org/jira/browse/FOR-364?page=comments#action_12312747 ] David Crossley commented on FOR-364: I don't know how you will be able to detect that the system is Windows and add that extra clarification. Perhaps Ant can detect the Operating System so that main/forrest.build.xml can add the extra message. Add Ctrl-C-Info to Jetty Startup-Messages - Key: FOR-364 URL: http://issues.apache.org/jira/browse/FOR-364 Project: Forrest Type: Improvement Components: Launch 'forrest run' Reporter: Ferdinand Soethe Priority: Minor At the moment it is guesswork how to properly end a forrest run session. Even more confusing that Ctrl-C (the only way to do it) will also trigger the query if you want to abort batch processing. A short info that is written just before the server is active should inform the user about the proper procedure: To stop the Forrest/Jetty server, press Ctrl-C, answer [N]o to the following question and press Enter to confirm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-524) The display of note and warning and fixme elements is broken.
The display of note and warning and fixme elements is broken. --- Key: FOR-524 URL: http://issues.apache.org/jira/browse/FOR-524 Project: Forrest Type: Bug Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev The special elements note and warning etc. are not being rendered as coloured boxes anymore. This was working recently, website was published okay on June 4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-524) The display of note and warning and fixme elements is broken.
[ http://issues.apache.org/jira/browse/FOR-524?page=comments#action_12312828 ] David Crossley commented on FOR-524: That is broken with the pelt skin. It is okay with the tigris skin. The display of note and warning and fixme elements is broken. --- Key: FOR-524 URL: http://issues.apache.org/jira/browse/FOR-524 Project: Forrest Type: Bug Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev The special elements note and warning etc. are not being rendered as coloured boxes anymore. This was working recently, website was published okay on June 4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-524) The display of note and warning and fixme elements is broken.
[ http://issues.apache.org/jira/browse/FOR-524?page=all ] David Crossley resolved FOR-524: Resolution: Fixed Oops, i must have been caught between svn revisions. Doing 'svn update' fixed it. Sorry for the noise. The display of note and warning and fixme elements is broken. --- Key: FOR-524 URL: http://issues.apache.org/jira/browse/FOR-524 Project: Forrest Type: Bug Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev The special elements note and warning etc. are not being rendered as coloured boxes anymore. This was working recently, website was published okay on June 4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-524) The display of note and warning and fixme elements is broken.
[ http://issues.apache.org/jira/browse/FOR-524?page=all ] David Crossley closed FOR-524: -- The display of note and warning and fixme elements is broken. --- Key: FOR-524 URL: http://issues.apache.org/jira/browse/FOR-524 Project: Forrest Type: Bug Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev The special elements note and warning etc. are not being rendered as coloured boxes anymore. This was working recently, website was published okay on June 4. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-527) The project.issues-rss-url in forrest.properties need to refer to apache.org
[ http://issues.apache.org/jira/browse/FOR-527?page=all ] David Crossley closed FOR-527: -- The project.issues-rss-url in forrest.properties need to refer to apache.org Key: FOR-527 URL: http://issues.apache.org/jira/browse/FOR-527 Project: Forrest Type: Bug Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev Following the move of Jira to apache.org Jira, our project.issues-rss-url needs adjustment. I have not yet been able to find the new URL. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-538) Clearer catalog instructions for Oxygen
[ http://issues.apache.org/jira/browse/FOR-538?page=all ] David Crossley closed FOR-538: -- Fix Version: 0.7-dev Resolution: Fixed Thanks, applied. Clearer catalog instructions for Oxygen --- Key: FOR-538 URL: http://issues.apache.org/jira/browse/FOR-538 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7-dev Environment: Oxygen 5.1 and 6.0 Reporter: Addison Berry Priority: Trivial Fix For: 0.7-dev Attachments: catalog.xml.diff While the current instructions will get you there if you know where to look for External Tools, Options is the main menu to start from in current versions of OxygenXML. I did simple patch on the word change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-391) website docs/site split
[ http://issues.apache.org/jira/browse/FOR-391?page=comments#action_12313406 ] David Crossley commented on FOR-391: We created a branch to find a better solution. See discussion: Re: release plan for 0.7 http://marc.theaimsgroup.com/?l=forrest-devm=111841994027073 ... which then went on to: Re: merge the docs-reorg branch (Was: release plan for 0.7) http://marc.theaimsgroup.com/?t=11185821544 website docs/site split --- Key: FOR-391 URL: http://issues.apache.org/jira/browse/FOR-391 Project: Forrest Type: Task Components: Documentation and website Versions: 0.7-dev Reporter: Dave Brondsema Assignee: David Crossley Fix For: 0.7-dev Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-391) website docs/site split
[ http://issues.apache.org/jira/browse/FOR-391?page=all ] David Crossley updated FOR-391: --- Attachment: reorg-1.png reorg-2.png reorg-1.png is screenshot showing 0.7 Docs tab with sub-tabs for other versions. reorg-2.png is screenshot showing is reult of selecting sub-tab 0.8-dev. website docs/site split --- Key: FOR-391 URL: http://issues.apache.org/jira/browse/FOR-391 Project: Forrest Type: Task Components: Documentation and website Versions: 0.7-dev Reporter: Dave Brondsema Assignee: David Crossley Fix For: 0.7-dev Attachments: reorg-1.png, reorg-2.png Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-355) Improved PDF configurability (e.g., TOC, Page Numbers, logo)
[ http://issues.apache.org/jira/browse/FOR-355?page=comments#action_12313412 ] David Crossley commented on FOR-355: Thanks Cyriaque, that is applied now. Your patches are a pleasure to work with. Improved PDF configurability (e.g., TOC, Page Numbers, logo) Key: FOR-355 URL: http://issues.apache.org/jira/browse/FOR-355 Project: Forrest Type: Improvement Components: Plugin: pdf-output Versions: 0.7-dev Reporter: Clay Leeds Assignee: David Crossley Priority: Minor Attachments: patchPageNumberingFormat.txt This change would probably involve skinconf.xml changes, as well as document2fo.xsl changes. It would be great to be able to configure the PDF output for the following options: - page numbers (ON/OFF) - more control over information in footer (ON/OFF, copyright info, credits) - Table of Contents generation (on a 1-page xdoc, it seems silly to generate a TOC page) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
[ http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12313425 ] David Crossley commented on FOR-506: Thanks, would you please do an 'svn update' and verify that the accented character is okay. Subversion reported conflicts for other reasons, so i applied it by hand. Also i tweaked it to be consistent with the others. I we change the colon spacing, we should be consistent. You might need to do 'svn revert CommonMessages_fr.xml' before you update. Do not hard-code site-visible message strings in skin files --- Key: FOR-506 URL: http://issues.apache.org/jira/browse/FOR-506 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.7-dev Environment: N/A Reporter: Pedro I. Sanchez Assignee: Thorsten Scherler Priority: Minor Attachments: frenchMessages.diff, newFrenchMessages.diff, patchI18n.diff Text strings like Copyright, Published, and Search are hardcoded into skin files like site2xhtml.xsl. When creating web sites in languages other than English the web developer is forced to create local versions of these skin files with the appropriated translations. Instead, the DTD for the skinconf.xml should be improved to allow these translations to be specified in this file. This would make Forrest much easier to use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-545) PDFs for the generated DTD documentation is going haywire
[ http://issues.apache.org/jira/browse/FOR-545?page=comments#action_12313880 ] David Crossley commented on FOR-545: The six documents are generated twice (for docs_0_70 and docs_0_60) so that is 12 extra minutes on the build time. I will move these docs up to the top-level at /dtdx/ because they don't need to be versioned. As a workaround for this PDF issue, created a project sitemap and added generated PDFs to the /dtdx/ directory. The project sitemap will serve these pre-prepared PDFs using the new technique for raw un-processed files. PDFs for the generated DTD documentation is going haywire - Key: FOR-545 URL: http://issues.apache.org/jira/browse/FOR-545 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7-dev Reporter: David Crossley Fix For: 0.7-dev We generate documentation for DTDs using the dtdx plugin. When the PDFs for this documentation are generated, it takes a long time to build them (about one minute each). Occasionally we see java.lang.OutOfMemoryError. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-391) website docs/site split
[ http://issues.apache.org/jira/browse/FOR-391?page=comments#action_12313936 ] David Crossley commented on FOR-391: This is done. Leaving issue open because we still need to adjust the .htaccess file. website docs/site split --- Key: FOR-391 URL: http://issues.apache.org/jira/browse/FOR-391 Project: Forrest Type: Task Components: Documentation and website Versions: 0.7-dev Reporter: Dave Brondsema Assignee: David Crossley Fix For: 0.7-dev Attachments: reorg-1.png, reorg-2.png, reorg-3.png, reorg-4.png, reorg-5.png Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-505) Allow the retrieval of raw html files
[ http://issues.apache.org/jira/browse/FOR-505?page=all ] David Crossley closed FOR-505: -- Resolution: Fixed Works for me now. See notes in upgrading_07.html Allow the retrieval of raw html files - Key: FOR-505 URL: http://issues.apache.org/jira/browse/FOR-505 Project: Forrest Type: Improvement Components: Core operations Versions: 0.7-dev Reporter: Ross Gardler Assignee: Ross Gardler Priority: Minor Fix For: 0.7-dev With the merging of the raw content directory and the xdocs directory it is no longer possible to retrieve the raw, unprocessed version of an HTML file. The raw HTML files were removed from the fresh-site in revision 178279. When we have added support for raw HTML files back into the system we should revive these files as a demo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-548) project DTD catalogs are not included when running as a servlet WAR
[ http://issues.apache.org/jira/browse/FOR-548?page=comments#action_12314189 ] David Crossley commented on FOR-548: One workaround is to add an additional path to the project CatalogManager.properties Change the default from this ... catalogs=../resources/schema/catalog.xcat to this ... catalogs=../resources/schema/catalog.xcat;../../project/src/documentation/resources/schema/catalog.xcat project DTD catalogs are not included when running as a servlet WAR --- Key: FOR-548 URL: http://issues.apache.org/jira/browse/FOR-548 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7-dev Reporter: David Crossley When using a WAR file under a full Jetty, the project catalog.xcat is not being included. The webapp has different paths (webapp/project/*) for the project resources. The src/documentation/classes/CatalogManager.properties file defines the relative path to the project catalog.xcat, which is then broken in a war. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-548) project DTD catalogs are not included when running as a servlet WAR
project DTD catalogs are not included when running as a servlet WAR --- Key: FOR-548 URL: http://issues.apache.org/jira/browse/FOR-548 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7-dev Reporter: David Crossley When using a WAR file under a full Jetty, the project catalog.xcat is not being included. The webapp has different paths (webapp/project/*) for the project resources. The src/documentation/classes/CatalogManager.properties file defines the relative path to the project catalog.xcat, which is then broken in a war. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-547) Plugins are not installed when calling forrest via Ant (forrest.build.xml:site)
[
http://issues.apache.org/jira/browse/FOR-547?page=comments#action_12314194 ]
David Crossley commented on FOR-547:
That link is broken, so here ...
http://marc.theaimsgroup.com/?t=11189653824
Plugins are not installed when calling forrest via Ant
(forrest.build.xml:site)
---
Key: FOR-547
URL: http://issues.apache.org/jira/browse/FOR-547
Project: Forrest
Type: Bug
Components: Core operations
Versions: 0.7-dev
Environment: Windows XP, SP2
Ant 1.6.5
Forrest 0.7rc1
Reporter: Ron Blaschke
Priority: Minor
I have an Ant script, which imports forrest.build.xml. When calling the site
target with a missing plugin, the install fails. But forrest init-plugins
works fine. Also, using versioned plugins works, using the Ant script and
forrest init-plugins..
Here's the relevant conversation from forrest-dev.
Ron Blaschke wrote:
Friday, June 17, 2005, 11:54:47 AM, Ross Gardler wrote:
Ron Blaschke wrote:
Unable to retrieve the ${plugin.name} plugin.
Two noteworthy things: Calling forrest init-plugins installs the
plugin sucessfully. And the error message says ${plugin.name},
instead of the real name of the plugin.
The two things are related. It looks like that the {plugin.name} is not
being set for some reason (and I guess {versioned.name} is not set either.
These are set in the init-plugins target of targets/plugins.xml
I ran my build.xml with ant -d, and found the following:
Setting ro project property: plugin.name - ${plugin.name}
Setting ro project property: plugin.version - ${plugin.version}
Setting ro project property: versioned.name -
org.apache.forrest.plugin.input.projectInfo
Actually that is as expected. The {plugin.name} and {plugin.version}
values are set by a regexp looking for the the version number. Since
there is no version number in the plugin required the regexp fails and
so no value for the property. The rest of the script tries to get the
{versioned.name} plugin. If it fails it falls back to the unversioned
plugin.
This explains why the error message shows ${plugin.name}, I've changed
that to use the {versioned.name} so at least it will give a more
meaningful error.
forrest -d says:
Setting ro project property: plugin.name -
org.apache.forrest.plugin.input.projectInfo
Setting ro project property: plugin.version -
Setting ro project property: versioned.name -
org.apache.forrest.plugin.input.projectInfo
This I don't understand. The bechaviour should be the same as above. The
relevant portion of the ANT script is at line 337 of targets/plugins.xml
My forrest.properties says this:
project.required.plugins=org.apache.forrest.plugin.input.projectInfo,
org.apache.forrest.plugin.input.simplifiedDocbook
I assume you get the same behaviour with simplifiedDocbook?
Out of curiosity, I added the plugin version.
project.required.plugins=org.apache.forrest.plugin.input.projectInfo-0.1,
org.apache.forrest.plugin.input.simplifiedDocbook
The debug trace of my build.xml changes to the following, and the
plugin is successfully installed.
Setting ro project property: plugin.name -
org.apache.forrest.plugin.input.projectInfo
Setting ro project property: plugin.version - 0.1
Setting ro project property: versioned.name -
org.apache.forrest.plugin.input.projectInfo-0.1
This looks like the behaviour expected.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Created: (FOR-549) plugin DTD catalogs are not included when running as a servlet WAR
plugin DTD catalogs are not included when running as a servlet WAR -- Key: FOR-549 URL: http://issues.apache.org/jira/browse/FOR-549 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7-dev Reporter: David Crossley When using a WAR file under a full Jetty, the plugins catalog.xcat files are not being included. In the webapp, the path to build/plugins/ is different. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-549) plugin DTD catalogs are not included when running as a servlet WAR
[ http://issues.apache.org/jira/browse/FOR-549?page=comments#action_12314198 ] David Crossley commented on FOR-549: The solution is to add an additional path to main/webapp/resources/schema/catalog.xcat like this ... nextCatalog catalog=../../build/plugins/catalog.xcat/ plugin DTD catalogs are not included when running as a servlet WAR -- Key: FOR-549 URL: http://issues.apache.org/jira/browse/FOR-549 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7-dev Reporter: David Crossley When using a WAR file under a full Jetty, the plugins catalog.xcat files are not being included. In the webapp, the path to build/plugins/ is different. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-549) plugin DTD catalogs are not included when running as a servlet WAR
[ http://issues.apache.org/jira/browse/FOR-549?page=all ] David Crossley updated FOR-549: --- Fix Version: 0.8-dev 0.7 Version: 0.8-dev plugin DTD catalogs are not included when running as a servlet WAR -- Key: FOR-549 URL: http://issues.apache.org/jira/browse/FOR-549 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7, 0.8-dev Reporter: David Crossley Fix For: 0.8-dev, 0.7 When using a WAR file under a full Jetty, the plugins catalog.xcat files are not being included. In the webapp, the path to build/plugins/ is different. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-550) build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat
[ http://issues.apache.org/jira/browse/FOR-550?page=all ] David Crossley updated FOR-550: --- Fix Version: 0.8-dev 0.7 Version: 0.7 0.8-dev build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat Key: FOR-550 URL: http://issues.apache.org/jira/browse/FOR-550 Project: Forrest Type: Bug Components: XML grammars validation Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev, 0.7 Attachments: plugins-catalog.txt The generated build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat which definitely breaks when using a war file and is not ideal in the other forrest methods. Patch attached which uses relative paths. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-550) build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat
[ http://issues.apache.org/jira/browse/FOR-550?page=all ] David Crossley closed FOR-550: -- Resolution: Fixed Fixed in both trunk and 0.7 branch. build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat Key: FOR-550 URL: http://issues.apache.org/jira/browse/FOR-550 Project: Forrest Type: Bug Components: XML grammars validation Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev, 0.7 Attachments: plugins-catalog.txt The generated build/plugins/catalog.xcat has full pathnames to each individual plugin catalog.xcat which definitely breaks when using a war file and is not ideal in the other forrest methods. Patch attached which uses relative paths. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-548) project DTD catalogs are not included when running as a servlet WAR
[ http://issues.apache.org/jira/browse/FOR-548?page=all ] David Crossley updated FOR-548: --- Fix Version: 0.8-dev 0.7 Version: 0.8-dev project DTD catalogs are not included when running as a servlet WAR --- Key: FOR-548 URL: http://issues.apache.org/jira/browse/FOR-548 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7, 0.8-dev Reporter: David Crossley Fix For: 0.8-dev, 0.7 When using a WAR file under a full Jetty, the project catalog.xcat is not being included. The webapp has different paths (webapp/project/*) for the project resources. The src/documentation/classes/CatalogManager.properties file defines the relative path to the project catalog.xcat, which is then broken in a war. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-548) project DTD catalogs are not included when running as a servlet WAR
[ http://issues.apache.org/jira/browse/FOR-548?page=all ] David Crossley resolved FOR-548: Resolution: Incomplete The two different paths were added to the fresh-site/src/documentation/classes/CatalogManager.properties This is a workaround, so the issue is marked as Incomplete. project DTD catalogs are not included when running as a servlet WAR --- Key: FOR-548 URL: http://issues.apache.org/jira/browse/FOR-548 Project: Forrest Type: Bug Components: Launch servlet WAR Versions: 0.7, 0.8-dev Reporter: David Crossley Fix For: 0.8-dev, 0.7 When using a WAR file under a full Jetty, the project catalog.xcat is not being included. The webapp has different paths (webapp/project/*) for the project resources. The src/documentation/classes/CatalogManager.properties file defines the relative path to the project catalog.xcat, which is then broken in a war. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-555) xml comments from html sources are no longer generated or are stripped
xml comments from html sources are no longer generated or are stripped -- Key: FOR-555 URL: http://issues.apache.org/jira/browse/FOR-555 Project: Forrest Type: Bug Components: Core operations Versions: 0.7, 0.8-dev Reporter: David Crossley Fix For: 0.7, 0.8-dev The old ihtml facility passed the xml comments through from the source html, the new behaviour does not. (The generated mirrors.html for our site-author was missing the special html comments that are parsed by mirrors.cgi script.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-391) website docs/site split
[ http://issues.apache.org/jira/browse/FOR-391?page=all ] David Crossley closed FOR-391: -- Fix Version: 0.8-dev Resolution: Fixed I have done some tweaks to the .htaccess. Nobody is reporting any problems with the new website, so closing this issue. website docs/site split --- Key: FOR-391 URL: http://issues.apache.org/jira/browse/FOR-391 Project: Forrest Type: Task Components: Documentation and website Versions: 0.7 Reporter: Dave Brondsema Assignee: David Crossley Fix For: 0.7, 0.8-dev Attachments: reorg-1.png, reorg-2.png, reorg-3.png, reorg-4.png, reorg-5.png Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-542) 'build test' should run validate-config target
[ http://issues.apache.org/jira/browse/FOR-542?page=all ] David Crossley closed FOR-542: -- Resolution: Fixed Done. 'build test' should run validate-config target Key: FOR-542 URL: http://issues.apache.org/jira/browse/FOR-542 Project: Forrest Type: Improvement Components: Compile Reporter: Thorsten Scherler Priority: Minor Fix For: 0.8-dev The validate-config target is only run by 'build release-dist'. We should make it also be run by 'build test' so that we detect any issues with stylesheets. Later. --David -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-561) jars in tools/eclipse/...lib need accompanying license
jars in tools/eclipse/...lib need accompanying license --- Key: FOR-561 URL: http://issues.apache.org/jira/browse/FOR-561 Project: Forrest Type: Task Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev All jars must follow the filename convention and also have an accompanying license with same-filename.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-564) Add the ability to create a What's New page always showing what's new for the latest release.
[ http://issues.apache.org/jira/browse/FOR-564?page=all ] David Crossley reassigned FOR-564: -- Assign To: David Crossley Add the ability to create a What's New page always showing what's new for the latest release. - Key: FOR-564 URL: http://issues.apache.org/jira/browse/FOR-564 Project: Forrest Type: Improvement Components: Plugin: projectInfo Versions: 0.8-dev Environment: Any Reporter: Cyriaque Dupoirieux Assignee: David Crossley Priority: Minor Attachments: patch564.txt A what's new page do not have to point to a specific version - or you will have to change at it every publication. i.e : **/releaseNotes_0.7.xml was our latest release but now it's **/releaseNotes_0.8-dev.xml So I add the ability to generate release notes or changes for the latest release : - Automatic generation of latest release notes by requesting **/releaseNotes_current.xml - Enable the generation of changes for the latest version by requesting **/changes_current.xml I send the patch in a few minutes... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-564) Add the ability to create a What's New page always showing what's new for the latest release.
[ http://issues.apache.org/jira/browse/FOR-564?page=all ] David Crossley closed FOR-564: -- Fix Version: 0.8-dev Resolution: Fixed Thanks, applied. Add the ability to create a What's New page always showing what's new for the latest release. - Key: FOR-564 URL: http://issues.apache.org/jira/browse/FOR-564 Project: Forrest Type: Improvement Components: Plugin: projectInfo Versions: 0.8-dev Environment: Any Reporter: Cyriaque Dupoirieux Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: patch564.txt A what's new page do not have to point to a specific version - or you will have to change at it every publication. i.e : **/releaseNotes_0.7.xml was our latest release but now it's **/releaseNotes_0.8-dev.xml So I add the ability to generate release notes or changes for the latest release : - Automatic generation of latest release notes by requesting **/releaseNotes_current.xml - Enable the generation of changes for the latest version by requesting **/changes_current.xml I send the patch in a few minutes... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-566) Option to Create a WAR file.
[ http://issues.apache.org/jira/browse/FOR-566?page=all ] David Crossley reassigned FOR-566: -- Assign To: David Crossley Option to Create a WAR file. Key: FOR-566 URL: http://issues.apache.org/jira/browse/FOR-566 Project: Forrest Type: New Feature Components: Tool: Eclipse config Reporter: Anil Ramnanan Assignee: David Crossley Attachments: org.apache.forrest.zip The option to create a war file should be added to the plugin's Site options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-566) Option to Create a WAR file.
[ http://issues.apache.org/jira/browse/FOR-566?page=all ] David Crossley reassigned FOR-566: -- Assign To: (was: David Crossley) Option to Create a WAR file. Key: FOR-566 URL: http://issues.apache.org/jira/browse/FOR-566 Project: Forrest Type: New Feature Components: Tool: Eclipse config Reporter: Anil Ramnanan Attachments: org.apache.forrest.zip The option to create a war file should be added to the plugin's Site options. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-534) Skin sample donation
[ http://issues.apache.org/jira/browse/FOR-534?page=all ] David Crossley updated FOR-534: --- Component: Skins (general issues) (was: Other) Skin sample donation Key: FOR-534 URL: http://issues.apache.org/jira/browse/FOR-534 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.6 Reporter: Torsten Stolpmann Priority: Minor Attachments: verit-forrest-sample.zip As discussed on dev@forrest.apache.org here are the skin sources to our forrest website. Please refer to the Notes.txt contained inside the attachment for further comments. Feedback welcome. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-565) site.xml Editor
[ http://issues.apache.org/jira/browse/FOR-565?page=all ] David Crossley reassigned FOR-565: -- Assign To: David Crossley site.xml Editor --- Key: FOR-565 URL: http://issues.apache.org/jira/browse/FOR-565 Project: Forrest Type: New Feature Components: Tool: Eclipse config Reporter: Anil Ramnanan Assignee: David Crossley Attachments: SiteXMLView.diff An editor witin the Eclipseplugin is needed for the site.xml file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-565) site.xml Editor
[ http://issues.apache.org/jira/browse/FOR-565?page=comments#action_12315035 ] David Crossley commented on FOR-565: Applied patch 1. SiteXMLView.diff (6 kb) site.xml Editor --- Key: FOR-565 URL: http://issues.apache.org/jira/browse/FOR-565 Project: Forrest Type: New Feature Components: Tool: Eclipse config Reporter: Anil Ramnanan Assignee: David Crossley Attachments: SiteXMLView.diff An editor witin the Eclipseplugin is needed for the site.xml file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-565) site.xml Editor
[ http://issues.apache.org/jira/browse/FOR-565?page=all ] David Crossley reassigned FOR-565: -- Assign To: (was: David Crossley) site.xml Editor --- Key: FOR-565 URL: http://issues.apache.org/jira/browse/FOR-565 Project: Forrest Type: New Feature Components: Tool: Eclipse config Reporter: Anil Ramnanan Attachments: SiteXMLView.diff An editor witin the Eclipseplugin is needed for the site.xml file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-568) Clearer forrestbot documentation
[ http://issues.apache.org/jira/browse/FOR-568?page=all ] David Crossley reassigned FOR-568: -- Assign To: David Crossley Clearer forrestbot documentation Key: FOR-568 URL: http://issues.apache.org/jira/browse/FOR-568 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7 Reporter: Addison Berry Assignee: David Crossley Priority: Minor Attachments: forrestbot.xml.diff The forrestbot documentation is not entirely clear to people not very familiar with ant and forrestbot workings. Some clarification for dummies like me would be much appreciated to make forrestbot implementation a little less painful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-568) Clearer forrestbot documentation
[ http://issues.apache.org/jira/browse/FOR-568?page=comments#action_12315195 ] David Crossley commented on FOR-568: Thanks, applied patch 1. forrestbot.xml.diff (7 kb). I then did a subsequent commit to convert tabs to spaces (please keep the same whitespace treament as the file already has). I also wrapped long lines. This is important, otherwise future diffs are impossible to read when paragraphs are one long line. Clearer forrestbot documentation Key: FOR-568 URL: http://issues.apache.org/jira/browse/FOR-568 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: Addison Berry Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: forrestbot.xml.diff The forrestbot documentation is not entirely clear to people not very familiar with ant and forrestbot workings. Some clarification for dummies like me would be much appreciated to make forrestbot implementation a little less painful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-568) Clearer forrestbot documentation
[ http://issues.apache.org/jira/browse/FOR-568?page=all ] David Crossley reassigned FOR-568: -- Assign To: (was: David Crossley) Clearer forrestbot documentation Key: FOR-568 URL: http://issues.apache.org/jira/browse/FOR-568 Project: Forrest Type: Improvement Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: Addison Berry Priority: Minor Fix For: 0.8-dev Attachments: forrestbot.xml.diff The forrestbot documentation is not entirely clear to people not very familiar with ant and forrestbot workings. Some clarification for dummies like me would be much appreciated to make forrestbot implementation a little less painful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-320) Additional navigation in head element
[ http://issues.apache.org/jira/browse/FOR-320?page=all ]
David Crossley updated FOR-320:
---
Fix Version: 0.8-dev
Description:
At least two users (myself included) need the ability to link to the previous
and next pages. This can be done by adding the follwoing to head
link rel=next href=nextPage.html /
link rel=prev href=prevPage.html /
next is the following page in the logical site.xml order.
prev is the previous page in the logical site.xml order
The skin then then choose to render this or not on a per page basis.
As a possible starting point I have a partial solution (it does not use link
elements and only does next):
xsl:template name=navigationLinks
xsl:if test=not($config/navigation/next/@enabled = 'false')
span class=navigation
xsl:for-each select=//[EMAIL PROTECTED]'menu']//[EMAIL
PROTECTED]'sel']
xsl:choose
xsl:when test=../following-sibling::*
xsl:variable name=linkText
xsl:value-of select=../following-sibling::*/
/xsl:variable
xsl:variable name=dirname
xsl:call-template name=dirname
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
xsl:variable name=filename
xsl:call-template name=filename
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
a class=dida
xsl:attribute name=hrefxsl:value-of
select=$dirname/xsl:value-of select=$filename//xsl:attribute
img class=skin src={$skin-img-dir}/next.gif
alt=Next:/
xsl:value-of select=$linkText/
/a
img class=spacer src={$spacer} alt= width=20
height=8 /
/xsl:when
xsl:otherwise
(Last in Section - choose a new section from the menu)
/xsl:otherwise
/xsl:choose
/xsl:for-each
/span
/xsl:if
/xsl:template
was:
At least two users (myself included) need the ability to link to the previous
and next pages. This can be done by adding the follwoing to head
link rel=next href=nextPage.html /
link rel=prev href=prevPage.html /
next is the following page in the logical site.xml order.
prev is the previous page in the logical site.xml order
The skin then then choose to render this or not on a per page basis.
As a possible starting point I have a partial solution (it does not use link
elements and only does next):
xsl:template name=navigationLinks
xsl:if test=not($config/navigation/next/@enabled = 'false')
span class=navigation
xsl:for-each select=//[EMAIL PROTECTED]'menu']//[EMAIL
PROTECTED]'sel']
xsl:choose
xsl:when test=../following-sibling::*
xsl:variable name=linkText
xsl:value-of select=../following-sibling::*/
/xsl:variable
xsl:variable name=dirname
xsl:call-template name=dirname
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
xsl:variable name=filename
xsl:call-template name=filename
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
a class=dida
xsl:attribute name=hrefxsl:value-of
select=$dirname/xsl:value-of select=$filename//xsl:attribute
img class=skin src={$skin-img-dir}/next.gif
alt=Next:/
xsl:value-of select=$linkText/
/a
img class=spacer src={$spacer} alt= width=20
height=8 /
/xsl:when
xsl:otherwise
(Last in Section - choose a new section from the menu)
/xsl:otherwise
/xsl:choose
/xsl:for-each
/span
/xsl:if
/xsl:template
Version: 0.7
0.8-dev
Environment:
Additional navigation in head element
-
Key: FOR-320
URL: http://issues.apache.org/jira/browse/FOR-320
Project: Forrest
Type: New Feature
Components: Skins (general issues)
Versions: 0.6, 0.7, 0.8-dev
Reporter: Ross Gardler
Priority: Trivial
Fix For: 0.8-dev
Attachments: patch320.txt
At least two users (myself included) need the ability to link to the previous
and next pages. This can be done by adding the follwoing to head
link rel=next href=nextPage.html /
link rel=prev href=prevPage.html /
next is the
[jira] Commented: (FOR-572) run a memory profiler while forrest is operating
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12315449 ] David Crossley commented on FOR-572: A couple of recent forrest-dev threads: [HEADS_UP] SVN HEAD is broken http://marc.theaimsgroup.com/?l=forrest-devm=112086829603887 possible memory problems http://marc.theaimsgroup.com/?l=forrest-devm=111958832520115 run a memory profiler while forrest is operating Key: FOR-572 URL: http://issues.apache.org/jira/browse/FOR-572 Project: Forrest Type: Task Components: Core operations Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-572) run a memory profiler while forrest is operating
run a memory profiler while forrest is operating Key: FOR-572 URL: http://issues.apache.org/jira/browse/FOR-572 Project: Forrest Type: Task Components: Core operations Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-320) Additional navigation in head element
[
http://issues.apache.org/jira/browse/FOR-320?page=comments#action_12315525 ]
David Crossley commented on FOR-320:
We need to make this configurable before we can apply this patch to the trunk
(unless i have misunderstood the effect). The demo looks like it will be very
useful. Thanks Cyriaque.
Additional navigation in head element
-
Key: FOR-320
URL: http://issues.apache.org/jira/browse/FOR-320
Project: Forrest
Type: New Feature
Components: Skins (general issues)
Versions: 0.6, 0.7, 0.8-dev
Reporter: Ross Gardler
Priority: Trivial
Fix For: 0.8-dev
Attachments: patch320.txt
At least two users (myself included) need the ability to link to the previous
and next pages. This can be done by adding the follwoing to head
link rel=next href=nextPage.html /
link rel=prev href=prevPage.html /
next is the following page in the logical site.xml order.
prev is the previous page in the logical site.xml order
The skin then then choose to render this or not on a per page basis.
As a possible starting point I have a partial solution (it does not use link
elements and only does next):
xsl:template name=navigationLinks
xsl:if test=not($config/navigation/next/@enabled = 'false')
span class=navigation
xsl:for-each select=//[EMAIL PROTECTED]'menu']//[EMAIL
PROTECTED]'sel']
xsl:choose
xsl:when test=../following-sibling::*
xsl:variable name=linkText
xsl:value-of select=../following-sibling::*/
/xsl:variable
xsl:variable name=dirname
xsl:call-template name=dirname
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
xsl:variable name=filename
xsl:call-template name=filename
xsl:with-param name=path
select=../following-sibling::*/a/@href/
/xsl:call-template
/xsl:variable
a class=dida
xsl:attribute name=hrefxsl:value-of
select=$dirname/xsl:value-of select=$filename//xsl:attribute
img class=skin src={$skin-img-dir}/next.gif
alt=Next:/
xsl:value-of select=$linkText/
/a
img class=spacer src={$spacer} alt= width=20
height=8 /
/xsl:when
xsl:otherwise
(Last in Section - choose a new section from the menu)
/xsl:otherwise
/xsl:choose
/xsl:for-each
/span
/xsl:if
/xsl:template
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (FOR-592) Pelt skin not HTML 4.01 compliant
[ http://issues.apache.org/jira/browse/FOR-592?page=all ] David Crossley updated FOR-592: --- Fix Version: 0.8-dev Version: 0.8-dev Pelt skin not HTML 4.01 compliant - Key: FOR-592 URL: http://issues.apache.org/jira/browse/FOR-592 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.7, 0.8-dev Reporter: Manuel Mall Fix For: 0.8-dev Just go to the Forrest home page and click the HTML 4.01 Compliance button. The page doesn't validate. Other sites, e.g. Apache FOP, created with the same skin have the same problem. One issue I could identify is that in the site2xhtml.xsl there are tags like: input type=submit value=Search name=Search i18n:attr=value/. The 'i18n:attr=value' bit creates a non HTML 4.01 compliant attribute. Other problems are related to Javascript not being escaped correctly, e.g. document.write(textLast Published:/text + document.lastModified); should be written as document.write(textLast Published:\/text + document.lastModified); I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant logo on the site is that the pages correctly validate. Pages based on this skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-592) Pelt skin not HTML 4.01 compliant
[ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317339 ] David Crossley commented on FOR-592: Our homepage did validate recently. You would need to track down which stylesheets are injecting these problems. Here is an example of how i find such things ... cd main find . -type f | xargs grep Last Published | grep -v \.svn ... shows that it is .../pelt/xslt/html/site2xhtml.xsl However, i suspect that it might be something to do with the internationalisation support. There were recently some changes for that. It seems like it is not transforming the i18n:text elements properly. Maybe because for the forrest/site-author/ we don't have i18n switched on. Try doing that by setting it on in forrest.properties and doing 'forrect run' and see what the difference is. The project.i18n property is described in ../main/fresh-site/forrest.properties To find out what changes were related to i18n recently, search the [EMAIL PROTECTED] mail archives for the commit messages. One way is via http://mail-archive.com/ and perhaps th edev list too. To find out which sitemaps deal with i18n, do ... cd main/webapp grep i18n *.* There is not a lot of documentation about i18n on the forrest website (search via our Google). Cheche has a document about it some )search full Google for cheche i18n. Hope that all helps. Pelt skin not HTML 4.01 compliant - Key: FOR-592 URL: http://issues.apache.org/jira/browse/FOR-592 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.7, 0.8-dev Reporter: Manuel Mall Fix For: 0.8-dev Just go to the Forrest home page and click the HTML 4.01 Compliance button. The page doesn't validate. Other sites, e.g. Apache FOP, created with the same skin have the same problem. One issue I could identify is that in the site2xhtml.xsl there are tags like: input type=submit value=Search name=Search i18n:attr=value/. The 'i18n:attr=value' bit creates a non HTML 4.01 compliant attribute. Other problems are related to Javascript not being escaped correctly, e.g. document.write(textLast Published:/text + document.lastModified); should be written as document.write(textLast Published:\/text + document.lastModified); I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant logo on the site is that the pages correctly validate. Pages based on this skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
[ http://issues.apache.org/jira/browse/FOR-506?page=comments#action_12317756 ] David Crossley commented on FOR-506: Some html validation issues ... Re: FOR-592 - pelt and i18n clarifications http://marc.theaimsgroup.com/?t=11231601642 Do not hard-code site-visible message strings in skin files --- Key: FOR-506 URL: http://issues.apache.org/jira/browse/FOR-506 Project: Forrest Type: Improvement Components: Skins (general issues) Versions: 0.7 Environment: N/A Reporter: Pedro I. Sanchez Assignee: Thorsten Scherler Priority: Minor Attachments: frenchMessages.diff, newFrenchMessages.diff, patchI18n.diff Text strings like Copyright, Published, and Search are hardcoded into skin files like site2xhtml.xsl. When creating web sites in languages other than English the web developer is forced to create local versions of these skin files with the appropriated translations. Instead, the DTD for the skinconf.xml should be improved to allow these translations to be specified in this file. This would make Forrest much easier to use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-592) Pelt skin not HTML 4.01 compliant
[ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12317757 ] David Crossley commented on FOR-592: Re: FOR-592 - pelt and i18n clarifications http://marc.theaimsgroup.com/?t=11231601642 Pelt skin not HTML 4.01 compliant - Key: FOR-592 URL: http://issues.apache.org/jira/browse/FOR-592 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.7, 0.8-dev Reporter: Manuel Mall Fix For: 0.8-dev Just go to the Forrest home page and click the HTML 4.01 Compliance button. The page doesn't validate. Other sites, e.g. Apache FOP, created with the same skin have the same problem. One issue I could identify is that in the site2xhtml.xsl there are tags like: input type=submit value=Search name=Search i18n:attr=value/. The 'i18n:attr=value' bit creates a non HTML 4.01 compliant attribute. Other problems are related to Javascript not being escaped correctly, e.g. document.write(textLast Published:/text + document.lastModified); should be written as document.write(textLast Published:\/text + document.lastModified); I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant logo on the site is that the pages correctly validate. Pages based on this skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-602) The 'build test' fails because does not load project XML Catalog
The 'build test' fails because does not load project XML Catalog Key: FOR-602 URL: http://issues.apache.org/jira/browse/FOR-602 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley The 'build test' cannot find the CatalogManager.properties and so it does not load the project XML Catalog. Then the parser fails to find some declared entities. All is okay when doing a 'forrest seed; forrest'. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=all ] David Crossley closed FOR-603: -- Fix Version: 0.8-dev Resolution: Fixed Wow, Addi, you are a champ. This is one of the most important documents that we could have on our website. Thanks for doing such a nice job of converting that mail list discussion. We need more of that type of effort. I left this issue open for a while because there sure to be more changes. There is another discussion happening on a related topic. Anyway I added your patch as-is, except that i converted tabs to two-space. I also folded long lines into about 80-characters wide. The reason for this is very important. I am now going to proceed to make some minor changes and you will see via the commit diffs (see www.mail-archive.com if you are not subscribed). If each paragraph was one enourmous long line, then it would be difficult to know the changes. (Yes i am adding stuff like that to a new how to be a developer document.) I have left this issue open for a while because there are sure to be more changes. The discussions are not finished. How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=all ] David Crossley reopened FOR-603: How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=all ] David Crossley reassigned FOR-603: -- Assign To: (was: David Crossley) How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=all ] David Crossley updated FOR-604: --- Attachment: 604-screenshot.png The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-604) The document-v* warning element does not get rendered properly
The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317891 ] David Crossley commented on FOR-604: Thanks for the research. I reckon it is not by deliberate design, rather a matter of inconsistent evolution. Glancing at the history http://svn.apache.org/viewcvs.cgi/forrest/trunk/main/webapp/skins/pelt/css/basic.css it seems that we had a warning and fixme defined in a certain way, and frame used for notes in another way. Yes please Gav, those box types should all be consistent, so please tweak the CSS to make them all look good like Note does. The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-221) NekoDTD generated dtd documentation needs improvement, some bugs
[ http://issues.apache.org/jira/browse/FOR-221?page=all ] David Crossley updated FOR-221: --- Comment: was deleted NekoDTD generated dtd documentation needs improvement, some bugs Key: FOR-221 URL: http://issues.apache.org/jira/browse/FOR-221 Project: Forrest Type: Improvement Components: Core operations Versions: 0.8-dev Reporter: David Crossley DTD Documentation http://forrest.apache.org/docs/dtd-docs.html Paraphrased from a discussion with Andy, i.e. his suggestions for some improvements. Bugs ... *) element declarations list in the table of contents are empty *) list of elements is alphabetic but the elements are not Enhancements ... *) sort the list of elements appearing in content model choice groups *) show parameter entity references in content models. Then, using JavaScript, the user could expand or collapse the content of the parameter entity. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=all ] David Crossley updated FOR-605: --- Attachment: 605-screenshot.png CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=all ] David Crossley reassigned FOR-604: -- Assign To: David Crossley The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Assignee: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png, basic.css.diff The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=comments#action_12317945 ] David Crossley commented on FOR-604: Thanks, applied your patch. I notice that there was unnecessary whitespace added, so i removed that. This will probably mean that you (Gavin) will get conflicts when you do 'svn update'. So either do 'svn revert basic.css' beforehand, or move the file out of the way and do 'svn update' again. I will leave this issue open in case you manage to do leather-dev css too. For the record, Gavin' s other questions above were answered on the dev list. The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Assignee: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png, basic.css.diff The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-604) The document-v* warning element does not get rendered properly
[ http://issues.apache.org/jira/browse/FOR-604?page=all ] David Crossley closed FOR-604: -- Resolution: Fixed Thanks, applied. I am closing this now. Regarding your other questions about viewHelper plugin, i suggest that your CSS skills would be best utilised to help Cyriaque, Thorsten, Diwaker, and others to generally improve the use of CSS within views. I am not clear about its use of the leather-dev skin, so best talk to them on the dev list. By the way, this patch would have been better created from the top-level, like you did with the pelt one (cd forrest; svn diff main/webapp/skins/pelt pelt-css.diff). In that way, the pathname of the files is in the diff and so i cannot possibly apply to the wrong source. This one just contained the name basic.css so is obscure. I see the problem with the whitespace is that the rest of the file is inconsistent. The document-v* warning element does not get rendered properly -- Key: FOR-604 URL: http://issues.apache.org/jira/browse/FOR-604 Project: Forrest Type: Bug Versions: 0.8-dev Reporter: David Crossley Assignee: David Crossley Fix For: 0.8-dev Attachments: 604-screenshot.png, basic.css.diff, basic.css.diff The warning element is rendered differently to the note element. Perhaps it only happens with the pelt skin - not yet verified. See screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-555) xml comments are no longer generated or are stripped
[ http://issues.apache.org/jira/browse/FOR-555?page=all ] David Crossley updated FOR-555: --- Summary: xml comments are no longer generated or are stripped (was: xml comments from html sources are no longer generated or are stripped) Description: The xml comments that are either in source documents or added via stylesheets are now being stripped. (The generated mirrors.html for our site-author is missing the special html comments that are parsed by mirrors.cgi script.) was: The old ihtml facility passed the xml comments through from the source html, the new behaviour does not. (The generated mirrors.html for our site-author was missing the special html comments that are parsed by mirrors.cgi script.) Updated the issue title and the description. The issue is more widespread than just html sources. xml comments are no longer generated or are stripped Key: FOR-555 URL: http://issues.apache.org/jira/browse/FOR-555 Project: Forrest Type: Bug Components: Core operations Versions: 0.7, 0.8-dev Reporter: David Crossley Fix For: 0.8-dev, 0.7 The xml comments that are either in source documents or added via stylesheets are now being stripped. (The generated mirrors.html for our site-author is missing the special html comments that are parsed by mirrors.cgi script.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-572) run a memory profiler while forrest is operating
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318434 ] David Crossley commented on FOR-572: Another separate discussion thread: Deeper Look at Memory Issue, Maybe Successful http://marc.theaimsgroup.com/?t=11237110818 run a memory profiler while forrest is operating Key: FOR-572 URL: http://issues.apache.org/jira/browse/FOR-572 Project: Forrest Type: Task Components: Core operations Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-572) run a memory profiler while forrest is operating
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12318565 ] David Crossley commented on FOR-572: Another separate discussion thread: Quick glimpse at Forrest's build times http://marc.theaimsgroup.com/?t=11237704496 run a memory profiler while forrest is operating Key: FOR-572 URL: http://issues.apache.org/jira/browse/FOR-572 Project: Forrest Type: Task Components: Core operations Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-627) Confiuration of Forrest
[ http://issues.apache.org/jira/browse/FOR-627?page=all ] David Crossley closed FOR-627: -- Resolution: Fixed Closed this and moved the comments over to the duplicate FOR-588 Confiuration of Forrest --- Key: FOR-627 URL: http://issues.apache.org/jira/browse/FOR-627 Project: Forrest Type: Improvement Components: Core operations Versions: 0.8-dev Reporter: Gavin Forrest's config files, as they stand have reached the end of their useful life. We are now limited in what we can do and views are making many of them redundant anyway. It is therefore proposed that we take this opportunity to simplify the config system. We had a design discussion about this and you can find Nicola's notes in SVN (see the hackathon directory in the etc directory of trunk). Together with the audio of our dicsussions (thanks David) Someone needs to summarise this discussion (Anil has stepped up to the plate on this one). NOTE: For any users thinking (oh no, the next forrest will be hard to upgrade because of fundamental changes in the way it is configured, don't worry. We will (most likely) provide tools to facilitate this upgrade, we will need them ourselves anyway). This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- http://issues.apache.org/jira/browse/FOR-618 Create issues for items discussed at Apachecon -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-588) Design new configuration system
[ http://issues.apache.org/jira/browse/FOR-588?page=all ] David Crossley updated FOR-588: --- Summary: Design new configuration system (was: Design new config system) Description: We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins. (was: We need a new config system for Forrest to enable the specification of multiple Forrest sites. within a single instance of Forrest and to accomodate the changes brought about by forrest:views, themes and plugins.) Design new configuration system --- Key: FOR-588 URL: http://issues.apache.org/jira/browse/FOR-588 Project: Forrest Type: Task Components: Core operations Reporter: Ross Gardler Priority: Blocker Fix For: 0.8-dev We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-634) Maintain Cocoons cache state between CLI invocations
[ http://issues.apache.org/jira/browse/FOR-634?page=all ] David Crossley updated FOR-634: --- Priority: Major (was: Minor) Maintain Cocoons cache state between CLI invocations Key: FOR-634 URL: http://issues.apache.org/jira/browse/FOR-634 Project: Forrest Type: Improvement Components: Core operations Versions: 0.8-dev Reporter: Ross Gardler As has been pointed out by Ferdinand () if we can make Cocoon maintain its cache between invocations forrest site we can considerably increase the performance of that command since subsections of pages (such as the navigation section) will only be regenerated when there is a change in that page. Similarly, pages will only be regenerated when they have changed. The question is can Cocoon maintain cache state between invocations? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory
images not reproduced in PDFs, if sources are in xdocs/images directory --- Key: FOR-635 URL: http://issues.apache.org/jira/browse/FOR-635 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev We used to enable images to be placed in the xdocs/images directory. However, now they are intended to go in the resources/images directory instead. Both methods will work for html pages, but only the latter method for the PDF pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-635) images not reproduced in PDFs, if sources are in xdocs/images directory
[ http://issues.apache.org/jira/browse/FOR-635?page=comments#action_12318971 ] David Crossley commented on FOR-635: Maybe i wasn't being clear. When forrest sees a URI that begins with images/*.* then it uses main/webapp/resources.xmap to look first in xdocs/images/ directory (for backwards compatibility) then in resources/images directory and elsewhere. That works fine for the html output, but not for PDFs. Sure, behind the scenes maybe Forrest maps those to absolute for FOP. However, ... I wonder if we should mark this issue as Won't fix and instead change our documentation and the example seed sites to encourage the use of the project resources directory instead instead of xdocs/images/ directory. images not reproduced in PDFs, if sources are in xdocs/images directory --- Key: FOR-635 URL: http://issues.apache.org/jira/browse/FOR-635 Project: Forrest Type: Bug Components: Documentation and website Versions: 0.7, 0.8-dev Reporter: David Crossley Priority: Minor Fix For: 0.8-dev We used to enable images to be placed in the xdocs/images directory. However, now they are intended to go in the resources/images directory instead. Both methods will work for html pages, but only the latter method for the PDF pages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=comments#action_12319173 ] David Crossley commented on FOR-603: Youch, i pressed the worng button and deleted it. Could you please re-attach. Whitespace inconsistencies cause havoc. Could we discuss that on the dev list please. How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=all ] David Crossley reassigned FOR-603: -- Assign To: David Crossley How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committed.xml.diff, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-603) How to become a Forrest Committer
[ http://issues.apache.org/jira/browse/FOR-603?page=comments#action_12319208 ] David Crossley commented on FOR-603: Added the patch committed.xml.diff (2 kb) How to become a Forrest Committer - Key: FOR-603 URL: http://issues.apache.org/jira/browse/FOR-603 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Addison Berry Assignee: David Crossley Priority: Minor Fix For: 0.8-dev Attachments: com.aart, committed.xml.diff, committer.xml Issue brought up on the mail list at http://marc.theaimsgroup.com/?l=forrest-devamp;m=112239074108858amp;w=2 re: creating documentation on becoming a committer in Forrest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-641) Ability to edit properties in Site.xml and tabs.xml editors
[ http://issues.apache.org/jira/browse/FOR-641?page=comments#action_12319673 ] David Crossley commented on FOR-641: Applied patch.220508.diff (15 kb) There were some minor troubles because your svn client seems to include your local pathnames in the patch. Ability to edit properties in Site.xml and tabs.xml editors --- Key: FOR-641 URL: http://issues.apache.org/jira/browse/FOR-641 Project: Forrest Type: New Feature Components: Tool: Eclipse config Versions: 0.8-dev Reporter: Anil Ramnanan Attachments: patch.220508.diff This includes a custom property view to allow you to edit the properties in the site.xml , tabs.xml and locationmap.xml files. This does not use Eclipse's build in properties editor since I am still trying to get that to work. This properties viwe will provide the fuctionality until I can get that working. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (FOR-636) Daisy Repository Browser
[ http://issues.apache.org/jira/browse/FOR-636?page=all ] David Crossley reassigned FOR-636: -- Assign To: David Crossley Daisy Repository Browser Key: FOR-636 URL: http://issues.apache.org/jira/browse/FOR-636 Project: Forrest Type: New Feature Components: Tool: Eclipse config Versions: 0.8-dev Reporter: Anil Ramnanan Assignee: David Crossley Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-636) Daisy Repository Browser
[ http://issues.apache.org/jira/browse/FOR-636?page=comments#action_12319683 ] David Crossley commented on FOR-636: Applied org.apache.forrest.repository.200805.zip Made some minor changes: * Added missing license header for one file. * Fix the copyright date on each file to be 2005. Also, did not commit the pre-compiled classes in the bin directory. Is that correct? Daisy Repository Browser Key: FOR-636 URL: http://issues.apache.org/jira/browse/FOR-636 Project: Forrest Type: New Feature Components: Tool: Eclipse config Versions: 0.8-dev Reporter: Anil Ramnanan Assignee: David Crossley Attachments: daisyPlugin.zip, org.apache.forrest.repository.200805.zip, org.apache.forrest.repository.daisy.180805.zip This is a plugin that will allow you to browse the Daisy repository, Functionality is limited to viewing all of the files on the repository. It does not include the functionality to add to a project's locationmap yet. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-642) forrest -projecthelp does not work when run from the root folder of Windows.
[ http://issues.apache.org/jira/browse/FOR-642?page=comments#action_12319689 ] David Crossley commented on FOR-642: Discussion is at http://thread.gmane.org/gmane.text.xml.forrest.user/2526 The user needs not run the 'forrest' command at the top-level directory. The 'forrest' commands should verify that there is content present (perhaps looking for forrest.properties file) before continuing. forrest -projecthelp does not work when run from the root folder of Windows. Key: FOR-642 URL: http://issues.apache.org/jira/browse/FOR-642 Project: Forrest Type: Bug Components: Launch 'forrest' Environment: Windows XP. Not tested on any other Operating System. Reporter: Anil Ramnanan If you try to run 'forrest -projecthelp' in the root of Windows, it gives an error C:\forrest -projecthelp BUILD FAILED Basedir C:\ -emacs -logger org.apache.tools.ant.NoBannerLogger -projecthelp do s not exist -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-643) Whitespace cleanup dir tree
[ http://issues.apache.org/jira/browse/FOR-643?page=all ] David Crossley closed FOR-643: -- Fix Version: 0.8-dev Resolution: Fixed Patch applied thanks. Whitespace cleanup dir tree --- Key: FOR-643 URL: http://issues.apache.org/jira/browse/FOR-643 Project: Forrest Type: Task Components: Other Versions: 0.8-dev Reporter: Addison Berry Priority: Minor Fix For: 0.8-dev Attachments: whitespace-cleanup.txt We will use a text directory tree doc to keep track of dirs as they are cleaned in our whitespace cleanup task. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-644) whitespace cleanup
whitespace cleanup -- Key: FOR-644 URL: http://issues.apache.org/jira/browse/FOR-644 Project: Forrest Type: Task Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev We have much inconsistent whitespace in all of our files. This is known to cause trouble in a collaborative environment. See discussion at: http://marc.theaimsgroup.com/?t=11245090111 and see the list at trunk/etc/whitespace-cleanup.txt This Issue will be used to announce which section of the repository is due to be cleaned next. Please keep discussion on that mail thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (FOR-645) patches for whitespace cleanup
patches for whitespace cleanup -- Key: FOR-645 URL: http://issues.apache.org/jira/browse/FOR-645 Project: Forrest Type: Sub-task Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Use this issue to provide patches for the whitespace cleanup. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-605) CSS enhancements needed for MOTD area inside Table of Contents
[ http://issues.apache.org/jira/browse/FOR-605?page=comments#action_12319954 ] David Crossley commented on FOR-605: That is an effect of just adding new features, without consolidating what we already have. At the last release, we urgently needed a way to show a prominent message, so i just added that without regard. The project would be very pleased if you would refine all the CSS and get some consistency. Just do whatever you see fit, do it in stages. Don't think that we actually designed the layout for large screens. In fact we want ideal rendering for all clients. CSS enhancements needed for MOTD area inside Table of Contents -- Key: FOR-605 URL: http://issues.apache.org/jira/browse/FOR-605 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Reporter: David Crossley Fix For: 0.8-dev Attachments: 605-screenshot.png, forrest_faq.png The Message of the Day (MOTD) facility inserts a panel at the top right of the Table of Contents (ToC). However this panel interferes with the flow of text in the ToC, forcing items to be line-wrapped to a narrow width. The MOTD is not properly implemented with CSS, probably needs its own definition. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-646) Corrected whitespace cleanup dir tree
[ http://issues.apache.org/jira/browse/FOR-646?page=all ] David Crossley closed FOR-646: -- Resolution: Fixed applied thanks. Corrected whitespace cleanup dir tree - Key: FOR-646 URL: http://issues.apache.org/jira/browse/FOR-646 Project: Forrest Type: Task Components: Other Versions: 0.8-dev Reporter: Addison Berry Priority: Trivial Attachments: whitespace-cleanup.txt.diff Redid the dir tree so that it is now more accurate and complete. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-647) Locationmap View needs to handle drop requests from the Repository Browser
[ http://issues.apache.org/jira/browse/FOR-647?page=all ] David Crossley closed FOR-647: -- Fix Version: 0.8-dev Resolution: Fixed applied thanks. Locationmap View needs to handle drop requests from the Repository Browser -- Key: FOR-647 URL: http://issues.apache.org/jira/browse/FOR-647 Project: Forrest Type: New Feature Components: Tool: Eclipse config Versions: 0.8-dev Reporter: Anil Ramnanan Fix For: 0.8-dev Attachments: locationmapView.240805.diff The Locationmap View needs to handle drop requests from the Repository Browser by creating the appropriate match and location elements. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-184) Switch to XHTML2
[ http://issues.apache.org/jira/browse/FOR-184?page=comments#action_12319977 ] David Crossley commented on FOR-184: Discussion started again: Planning the move to XHTML2 http://marc.theaimsgroup.com/?t=11239291561 XHTML2 - let's do it! http://marc.theaimsgroup.com/?t=11248949717 XHTML2 http://marc.theaimsgroup.com/?t=11248726404 Switch to XHTML2 Key: FOR-184 URL: http://issues.apache.org/jira/browse/FOR-184 Project: Forrest Type: New Feature Components: XML grammars validation Versions: 0.6 Reporter: Nicola Ken Barozzi Fix For: 0.8-dev Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations and will force to write new skins for this format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-184) Switch to XHTML2
[ http://issues.apache.org/jira/browse/FOR-184?page=all ] David Crossley updated FOR-184: --- Component: Core operations (was: XML grammars validation) Version: 0.8-dev (was: 0.6) Environment: Switch to XHTML2 Key: FOR-184 URL: http://issues.apache.org/jira/browse/FOR-184 Project: Forrest Type: New Feature Components: Core operations Versions: 0.8-dev Reporter: Nicola Ken Barozzi Fix For: 0.8-dev Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations and will force to write new skins for this format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (FOR-650) MOTD Needs to have a working example.
[ http://issues.apache.org/jira/browse/FOR-650?page=all ] David Crossley resolved FOR-650: Fix Version: 0.8-dev Resolution: Fixed Patch applied, thanks. Careful, it also removed the link3 element from the breadtrail. I also tweaked the explanatory text, and showed that the appending to html/title can be avoided. MOTD Needs to have a working example. - Key: FOR-650 URL: http://issues.apache.org/jira/browse/FOR-650 Project: Forrest Type: Sub-task Components: Skins (general issues) Versions: 0.8-dev Environment: All Reporter: Gavin Priority: Minor Fix For: 0.8-dev Attachments: faq.xml.diff, skinconf.xml.diff MOTD area example code in skinconf.xml does not work 'out of the box' but requires subtle changes to get it to work. A very brief explanation and pointer should be in the samples/faq to show the way. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-592) Pelt skin not HTML 4.01 compliant
[ http://issues.apache.org/jira/browse/FOR-592?page=comments#action_12320350 ] David Crossley commented on FOR-592: The discussion thread above, explored various workarounds. The easiest is to have a simple transformer to strip the i18n:text elements that remain if i18n processing is not enabled. This is now added to the trunk at r263870. Pelt skin not HTML 4.01 compliant - Key: FOR-592 URL: http://issues.apache.org/jira/browse/FOR-592 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.7, 0.8-dev Reporter: Manuel Mall Fix For: 0.8-dev Just go to the Forrest home page and click the HTML 4.01 Compliance button. The page doesn't validate. Other sites, e.g. Apache FOP, created with the same skin have the same problem. One issue I could identify is that in the site2xhtml.xsl there are tags like: input type=submit value=Search name=Search i18n:attr=value/. The 'i18n:attr=value' bit creates a non HTML 4.01 compliant attribute. Other problems are related to Javascript not being escaped correctly, e.g. document.write(textLast Published:/text + document.lastModified); should be written as document.write(textLast Published:\/text + document.lastModified); I assume a requirement of being allowed to put the W3C HTML 4.01 Compliant logo on the site is that the pages correctly validate. Pages based on this skin don't validate but do carry the logo. Sounds like a problem to me. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-649) [PATCH] hlink and vlink colors are not set correctly
[ http://issues.apache.org/jira/browse/FOR-649?page=all ] David Crossley updated FOR-649: --- Fix Version: 0.8-dev Version: 0.8-dev (was: 0.11) [PATCH] hlink and vlink colors are not set correctly Key: FOR-649 URL: http://issues.apache.org/jira/browse/FOR-649 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Environment: n/a Reporter: Dave Brosius Priority: Minor Fix For: 0.8-dev Attachments: fix_bad_assigns.diff code sets up hlink and vlink variables but never uses them to set hlink and vlink colors. Uses 'link' variable instead. Patch fixes this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (FOR-649) [PATCH] hlink and vlink colors are not set correctly
[ http://issues.apache.org/jira/browse/FOR-649?page=all ] David Crossley closed FOR-649: -- Resolution: Fixed Patch applied. Thanks. [PATCH] hlink and vlink colors are not set correctly Key: FOR-649 URL: http://issues.apache.org/jira/browse/FOR-649 Project: Forrest Type: Bug Components: Skins (general issues) Versions: 0.8-dev Environment: n/a Reporter: Dave Brosius Priority: Minor Fix For: 0.8-dev Attachments: fix_bad_assigns.diff code sets up hlink and vlink variables but never uses them to set hlink and vlink colors. Uses 'link' variable instead. Patch fixes this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-572) run a memory profiler while forrest is operating
[ http://issues.apache.org/jira/browse/FOR-572?page=comments#action_12320521 ] David Crossley commented on FOR-572: Thanks. Applied patch step1_profiling.patch (3 kb) run a memory profiler while forrest is operating Key: FOR-572 URL: http://issues.apache.org/jira/browse/FOR-572 Project: Forrest Type: Task Components: Core operations Versions: 0.8-dev Reporter: David Crossley Priority: Critical Fix For: 0.8-dev Attachments: step1_profiling.patch We need to run a memory profiler while forrest is operating. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-184) Switch to XHTML2
[ http://issues.apache.org/jira/browse/FOR-184?page=comments#action_12320559 ] David Crossley commented on FOR-184: Subtasks were added as aresult of this thread: Re: Planning the move to XHTML2 (Re: (FOR-184) Switch to XHTML2)) http://marc.theaimsgroup.com/?t=11251273582 Switch to XHTML2 Key: FOR-184 URL: http://issues.apache.org/jira/browse/FOR-184 Project: Forrest Type: New Feature Components: Core operations Versions: 0.8-dev Reporter: Nicola Ken Barozzi Fix For: 0.8-dev Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations and will force to write new skins for this format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-655) Create sample document for XHTML2 subset
[ http://issues.apache.org/jira/browse/FOR-655?page=all ] David Crossley updated FOR-655: --- Fix Version: 0.8-dev Description: Define the set of XHTML2 modules that will be used and document those by example. See discussion in thread: Re: XHTML2 - let's do it! http://marc.theaimsgroup.com/?t=11248949717 Version: 0.8-dev Environment: Create sample document for XHTML2 subset Key: FOR-655 URL: http://issues.apache.org/jira/browse/FOR-655 Project: Forrest Type: Sub-task Versions: 0.8-dev Reporter: Ross Gardler Fix For: 0.8-dev Define the set of XHTML2 modules that will be used and document those by example. See discussion in thread: Re: XHTML2 - let's do it! http://marc.theaimsgroup.com/?t=11248949717 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-608) Document Modify plugins and project config options of Eclipse tool
[ http://issues.apache.org/jira/browse/FOR-608?page=comments#action_12320643 ] David Crossley commented on FOR-608: Patch applied thanks: eclipse.300805.diff (4 kb) Document Modify plugins and project config options of Eclipse tool -- Key: FOR-608 URL: http://issues.apache.org/jira/browse/FOR-608 Project: Forrest Type: Improvement Components: Documentation and website Reporter: Ross Gardler Fix For: 0.8-dev Attachments: eclipse.300805.diff Features added in FOR-596 need to be documented -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (FOR-184) Switch to XHTML2
[ http://issues.apache.org/jira/browse/FOR-184?page=comments#action_12320761 ] David Crossley commented on FOR-184: See the description of the processing pipeline in trunk/site-author/content/xdocs/TR/2004/WD-forrest10.html Switch to XHTML2 Key: FOR-184 URL: http://issues.apache.org/jira/browse/FOR-184 Project: Forrest Type: New Feature Components: Core operations Versions: 0.8-dev Reporter: Nicola Ken Barozzi Fix For: 0.8-dev Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations and will force to write new skins for this format. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (FOR-184) Switch to XHTML2
[ http://issues.apache.org/jira/browse/FOR-184?page=all ] David Crossley updated FOR-184: --- Description: Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations, new sitemap pipelines, new stylesheets, new input/output for views. See the steps in thread: http://marc.theaimsgroup.com/?t=11251273582 (was: Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations and will force to write new skins for this format.) Switch to XHTML2 Key: FOR-184 URL: http://issues.apache.org/jira/browse/FOR-184 Project: Forrest Type: New Feature Components: Core operations Versions: 0.8-dev Reporter: Nicola Ken Barozzi Fix For: 0.8-dev Switch to using XHTML2 as a base and intermediate format. This means also using RelaxNG validations, new sitemap pipelines, new stylesheets, new input/output for views. See the steps in thread: http://marc.theaimsgroup.com/?t=11251273582 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
