[JIRA] Updated: (FOR-510) Setting Environment Variables Information
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 3 Jun 2005 5:09 AM Changes: Fix Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-510?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-510 Here is an overview of the issue: - Key: FOR-510 Summary: Setting Environment Variables Information Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Addison Berry Created: Sat, 28 May 2005 8:53 AM Updated: Fri, 3 Jun 2005 5:09 AM Description: 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 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-514) Do not limit status.xml contexts in project info plugin
The following issue has been updated:
Updater: Cyriaque Dupoirieux (mailto:[EMAIL PROTECTED])
Date: Fri, 3 Jun 2005 7:41 AM
Comment:
- 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)
Regards,
Cyriaque,
Changes:
Attachment changed to patch.txt
-
For a full history of the issue, see:
http://issues.cocoondev.org//browse/FOR-514?page=history
-
View the issue:
http://issues.cocoondev.org//browse/FOR-514
Here is an overview of the issue:
-
Key: FOR-514
Summary: Do not limit status.xml contexts in project info plugin
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Plugin: projectInfo
Assignee:
Reporter: Ross Gardler
Created: Wed, 1 Jun 2005 6:02 AM
Updated: Fri, 3 Jun 2005 7:41 AM
Description:
(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,
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-516) motd in image area looks incorrect
The following issue has been updated: Updater: kevin (mailto:[EMAIL PROTECTED]) Date: Fri, 3 Jun 2005 1:23 PM Comment: Patch if my fix ok. Changes: Attachment changed to skinconf.xml.diff - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-516?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-516 Here is an overview of the issue: - Key: FOR-516 Summary: motd in image area looks incorrect Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: photoGallery Versions: 0.7-dev Assignee: Reporter: kevin Created: Fri, 3 Jun 2005 1:21 PM Updated: Fri, 3 Jun 2005 1:23 PM Environment: Any Description: Generates a working site but motd in image area looks incorrect. Suggest in plugin skinconf.xml motd-page location=alt Kevin. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-516) motd in image area looks incorrect
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-516 Here is an overview of the issue: - Key: FOR-516 Summary: motd in image area looks incorrect Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: photoGallery Versions: 0.7-dev Assignee: Reporter: kevin Created: Fri, 3 Jun 2005 1:21 PM Updated: Fri, 3 Jun 2005 1:21 PM Environment: Any Description: Generates a working site but motd in image area looks incorrect. Suggest in plugin skinconf.xml motd-page location=alt Kevin. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-189) Ad charting capability to Forrest
Message: The following issue has been closed. Resolver: Ross Gardler Date: Thu, 2 Jun 2005 8:47 AM See the Chart output plugin - View the issue: http://issues.cocoondev.org//browse/FOR-189 Here is an overview of the issue: - Key: FOR-189 Summary: Ad charting capability to Forrest Type: New Feature Status: Closed Priority: Major Resolution: FIXED Project: Forrest Components: Core operations Assignee: Ross Gardler Reporter: Nicola Ken Barozzi Created: Thu, 10 Jun 2004 5:26 PM Updated: Thu, 2 Jun 2005 8:47 AM Description: JCharts has an xml input format, so it should be easy to add this feature to Forrest. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-515) Duplicate year in Pelt copyright text
The following issue has been updated: Updater: Addison Berry (mailto:[EMAIL PROTECTED]) Date: Thu, 2 Jun 2005 6:10 PM Comment: Attached a patch that removes the duplicate year that is within the otherwise clause. This makes the year always appear as non-link text, one time regardless if there is a copyright-link or not. Changes: Attachment changed to site2xhtml.xsl.diff - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-515?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-515 Here is an overview of the issue: - Key: FOR-515 Summary: Duplicate year in Pelt copyright text Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Addison Berry Created: Thu, 2 Jun 2005 6:06 PM Updated: Thu, 2 Jun 2005 6:10 PM Description: The copyright year is duplicated in pelt. It appears twice in the site2xhtml.xsl file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-515) Duplicate year in Pelt copyright text
The following comment has been added to this issue: Author: Addison Berry Created: Thu, 2 Jun 2005 6:14 PM Body: Note that Tim Williams found the bug in the file originally. - View this comment: http://issues.cocoondev.org//browse/FOR-515?page=comments#action_12471 - View the issue: http://issues.cocoondev.org//browse/FOR-515 Here is an overview of the issue: - Key: FOR-515 Summary: Duplicate year in Pelt copyright text Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Addison Berry Created: Thu, 2 Jun 2005 6:06 PM Updated: Thu, 2 Jun 2005 6:14 PM Description: The copyright year is duplicated in pelt. It appears twice in the site2xhtml.xsl file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-515) Duplicate year in Pelt copyright text
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Thu, 2 Jun 2005 6:51 PM Changes: Fix Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-515?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-515 Here is an overview of the issue: - Key: FOR-515 Summary: Duplicate year in Pelt copyright text Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: Addison Berry Created: Thu, 2 Jun 2005 6:06 PM Updated: Thu, 2 Jun 2005 6:51 PM Description: The copyright year is duplicated in pelt. It appears twice in the site2xhtml.xsl file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-487) generate announcement text from the status.xml
The following comment has been added to this issue:
Author: Cyriaque Dupoirieux
Created: Wed, 1 Jun 2005 5:34 AM
Body:
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,
-
View this comment:
http://issues.cocoondev.org//browse/FOR-487?page=comments#action_12458
-
View the issue:
http://issues.cocoondev.org//browse/FOR-487
Here is an overview of the issue:
-
Key: FOR-487
Summary: generate announcement text from the status.xml
Type: New Feature
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Forrest
Components:
Plugins (general issues)
Fix Fors:
0.7-dev
Versions:
0.7-dev
Assignee: Ross Gardler
Reporter: David Crossley
Created: Wed, 27 Apr 2005 11:23 PM
Updated: Wed, 1 Jun 2005 5:34 AM
Description:
By adding some attributes to the actions in status.xml we would be able to
use certain entries for the announcement text.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-487) generate announcement text from the status.xml
The following comment has been added to this issue: Author: Ross Gardler Created: Wed, 1 Jun 2005 6:02 AM Body: I've moved this to a new issue as this one has been closed, see FOR-514. - View this comment: http://issues.cocoondev.org//browse/FOR-487?page=comments#action_12459 - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Wed, 1 Jun 2005 6:02 AM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-514) Do not limit status.xml contexts in project info plugin
The following comment has been added to this issue:
Author: Ross Gardler
Created: Wed, 1 Jun 2005 6:07 AM
Body:
In one sense you change is a big improvement on my original code. However, it
prevents the ability to add a meningful title to each section since the title
becomes the value of the context attribute.
Perhaps we can provide an (optional) lookup table in the status.xml file that
will give a title, for example:
status
actionContexts
context id=code description=Changes to the Code Base
context id=docs description=Changes to the Documentation
/action
...
status
If no entry is found for //actionContexts/[EMAIL PROTECTED]CONTEXT] then we
would use the @id value in titles otherwise we would use
//actionContexts/[EMAIL PROTECTED]CONTEXT]/@description
In later versions this would allow for internationalisation of the status
contexts.
WDYT?
[NB try to submite changes as patched, it makes it much easier for us to apply
and therefore increases the chance of it being applied in a timely fashion. If
you don't know how ask us on the dev list.]
-
View this comment:
http://issues.cocoondev.org//browse/FOR-514?page=comments#action_12460
-
View the issue:
http://issues.cocoondev.org//browse/FOR-514
Here is an overview of the issue:
-
Key: FOR-514
Summary: Do not limit status.xml contexts in project info plugin
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Plugin: projectInfo
Assignee:
Reporter: Ross Gardler
Created: Wed, 1 Jun 2005 6:02 AM
Updated: Wed, 1 Jun 2005 6:07 AM
Description:
(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,
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-514) Do not limit status.xml contexts in project info plugin
The following comment has been added to this issue:
Author: Cyriaque Dupoirieux
Created: Wed, 1 Jun 2005 8:45 AM
Body:
Good Ross,
I can work on it with your idea :
actionContexts
context id=code description=Changes to the Code Base
context id=docs description=Changes to the Documentation
/actionContexts
And I will send a patch.
By the way, I could not - in my previous comment - send a patch because the
issue were closed... (that's why I send a code sample in the text...)
-
View this comment:
http://issues.cocoondev.org//browse/FOR-514?page=comments#action_12462
-
View the issue:
http://issues.cocoondev.org//browse/FOR-514
Here is an overview of the issue:
-
Key: FOR-514
Summary: Do not limit status.xml contexts in project info plugin
Type: Improvement
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Plugin: projectInfo
Assignee:
Reporter: Ross Gardler
Created: Wed, 1 Jun 2005 6:02 AM
Updated: Wed, 1 Jun 2005 8:45 AM
Description:
(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,
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-513) Messages from Cocoon about Lazy mode
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-513 Here is an overview of the issue: - Key: FOR-513 Summary: Messages from Cocoon about Lazy mode Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Mon, 30 May 2005 7:38 PM Updated: Mon, 30 May 2005 7:38 PM Description: Cocoon issues messages Lazy mode: true etc. These are issued when Cocoon loads a sitemap component. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-513) Messages from Cocoon about Lazy mode
The following comment has been added to this issue: Author: David Crossley Created: Mon, 30 May 2005 7:44 PM Body: The reason that we are seeing these messages is probably because we are using a version of Cocoon that still contains debug statements about this facility. The messages can be ignored. Lazy mode: true means that Cocoon will only load each sitemap component when it is actually required. This helps to speed Cocoon startup. Forrest has configured Lazy mode: true for the 'forrest site' and Lazy mode: false for the 'forrest run'. - View this comment: http://issues.cocoondev.org//browse/FOR-513?page=comments#action_12452 - View the issue: http://issues.cocoondev.org//browse/FOR-513 Here is an overview of the issue: - Key: FOR-513 Summary: Messages from Cocoon about Lazy mode Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Mon, 30 May 2005 7:38 PM Updated: Mon, 30 May 2005 7:44 PM Description: Cocoon issues messages Lazy mode: true etc. These are issued when Cocoon loads a sitemap component. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-505) Allow the retrieval of raw html files
The following comment has been added to this issue: Author: David Crossley Created: Mon, 30 May 2005 8:41 PM Body: Discussion about a solution is at: http://marc.theaimsgroup.com/?t=11169681410 - View this comment: http://issues.cocoondev.org//browse/FOR-505?page=comments#action_12453 - View the issue: http://issues.cocoondev.org//browse/FOR-505 Here is an overview of the issue: - Key: FOR-505 Summary: Allow the retrieval of raw html files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Tue, 24 May 2005 3:53 PM Updated: Mon, 30 May 2005 8:41 PM Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-511) Need better documentation explaining how to use Tabs
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-511 Here is an overview of the issue: - Key: FOR-511 Summary: Need better documentation explaining how to use Tabs Type: Improvement Status: Unassigned Priority: Major Project: Forrest Components: Documentation and website Assignee: Reporter: David Crossley Created: Sun, 29 May 2005 1:20 AM Updated: Sun, 29 May 2005 1:20 AM Description: Subject: Re: documentation additions and issue tracking (Was: App vs Data) Date: Sat, 28 May 2005 To: forrest-user http://mail-archives.apache.org/mod_mbox/forrest-user/200505.mbox/[EMAIL PROTECTED] - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-511) Need better documentation explaining how to use Tabs
The following issue has been updated: Updater: David Crossley (mailto:[EMAIL PROTECTED]) Date: Sun, 29 May 2005 1:21 AM Changes: description changed from Subject: Re: documentation additions and issue tracking (Was: App vs Data) Date: Sat, 28 May 2005 To: forrest-user http://mail-archives.apache.org/mod_mbox/forrest-user/200505.mbox/[EMAIL PROTECTED] to Subject: Re: documentation additions and issue tracking (Was: App vs Data) Date: Sat, 28 May 2005 http://www.mail-archive.com/user%40forrest.apache.org/msg00650.html - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-511?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-511 Here is an overview of the issue: - Key: FOR-511 Summary: Need better documentation explaining how to use Tabs Type: Improvement Status: Unassigned Priority: Major Project: Forrest Components: Documentation and website Assignee: Reporter: David Crossley Created: Sun, 29 May 2005 1:20 AM Updated: Sun, 29 May 2005 1:21 AM Description: Subject: Re: documentation additions and issue tracking (Was: App vs Data) Date: Sat, 28 May 2005 http://www.mail-archive.com/user%40forrest.apache.org/msg00650.html - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-512) Need documentation explaining how to use site.xml configuration file
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-512 Here is an overview of the issue: - Key: FOR-512 Summary: Need documentation explaining how to use site.xml configuration file Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Assignee: Reporter: David Crossley Created: Sun, 29 May 2005 1:23 AM Updated: Sun, 29 May 2005 1:23 AM Description: Subject: Re: documentation additions and issue tracking (Was: App vs Data) Date: Sat, 28 May 2005 http://www.mail-archive.com/user%40forrest.apache.org/msg00650.html - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-510) Setting Environment Variables Information
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-510 Here is an overview of the issue: - Key: FOR-510 Summary: Setting Environment Variables Information Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Versions: 0.6 Assignee: Reporter: Addison Berry Created: Sat, 28 May 2005 8:53 AM Updated: Sat, 28 May 2005 8:53 AM Description: 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 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-510) Setting Environment Variables Information
The following comment has been added to this issue: Author: Addison Berry Created: Sat, 28 May 2005 9:17 AM Body: This instruction 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 should be changed slightly for Windows XP to read: Go to My Computer, Properties, Advanced, Environment Variables Create a New variable with name: FORREST_HOME value: C:\full\path\to\apache-forrest-0.7 then Edit PATH by adding ;%FORREST_HOME%\bin to the end of the current value. - View this comment: http://issues.cocoondev.org//browse/FOR-510?page=comments#action_12445 - View the issue: http://issues.cocoondev.org//browse/FOR-510 Here is an overview of the issue: - Key: FOR-510 Summary: Setting Environment Variables Information Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Versions: 0.6 Assignee: Reporter: Addison Berry Created: Sat, 28 May 2005 8:53 AM Updated: Sat, 28 May 2005 9:17 AM Description: 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 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-508) available-skins command returns incorrect information
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-508 Here is an overview of the issue: - Key: FOR-508 Summary: available-skins command returns incorrect information Type: Task Status: Unassigned Priority: Minor Project: Forrest Versions: 0.6 Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:27 AM Updated: Fri, 27 May 2005 5:27 AM Environment: Win XP (but I don't think that matters in this case). Description: Forrest available-skins command returns incorrect information, including a skin (crust) which no longer exists, and omitting some (plain-dev, leather-dev) which are available (but not fully supported). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-509) Deprecated skin designated to replace non-existant skin
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-509 Here is an overview of the issue: - Key: FOR-509 Summary: Deprecated skin designated to replace non-existant skin Type: Task Status: Unassigned Priority: Minor Project: Forrest Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:51 AM Updated: Fri, 27 May 2005 5:51 AM Description: In forrest.build.xml, a skin-aliasing occurs to replace skins which no longer exist by an alternative, and a warning is issued. Similarly, a warning is issued when a deprecated skin is chosen. It can happen that a deprecated skin is designated to replace a no-longer-existing skin: this should be avoided to prevent confusion. Maintenance should ensure that only non-deprecated (i.e. supported) skins are designated replacements each time the build file is updated or skins are deprecated. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-509) Deprecated skin designated to replace non-existant skin
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 27 May 2005 6:28 AM Comment: Scheduled for 0.7 release Changes: type changed from Task to Improvement Version changed to 0.6 Component changed to Skins (general issues) Fix Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-509?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-509 Here is an overview of the issue: - Key: FOR-509 Summary: Deprecated skin designated to replace non-existant skin Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:51 AM Updated: Fri, 27 May 2005 6:28 AM Description: In forrest.build.xml, a skin-aliasing occurs to replace skins which no longer exist by an alternative, and a warning is issued. Similarly, a warning is issued when a deprecated skin is chosen. It can happen that a deprecated skin is designated to replace a no-longer-existing skin: this should be avoided to prevent confusion. Maintenance should ensure that only non-deprecated (i.e. supported) skins are designated replacements each time the build file is updated or skins are deprecated. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-508) available-skins command returns incorrect information
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 27 May 2005 6:25 AM Comment: Reclassified to be fixed in the 0.7 release Changes: type changed from Task to Bug priority changed from Minor to Major Component changed to Skins (general issues) Fix Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-508?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-508 Here is an overview of the issue: - Key: FOR-508 Summary: available-skins command returns incorrect information Type: Bug Status: Unassigned Priority: Major Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:27 AM Updated: Fri, 27 May 2005 6:25 AM Environment: Win XP (but I don't think that matters in this case). Description: Forrest available-skins command returns incorrect information, including a skin (crust) which no longer exists, and omitting some (plain-dev, leather-dev) which are available (but not fully supported). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-509) Deprecated skin designated to replace non-existant skin
The following issue has been updated: Updater: Tim Williams (mailto:[EMAIL PROTECTED]) Date: Fri, 27 May 2005 9:13 AM Comment: Unless I've oversimplified this, here's the change for this. crust now goes to pelt. Skin aliasing for backwards compatability 0.5 = 0.6 krysalis-site = ... warn about future removal forrest-site = ... warn about future removal crust = pelt forrest-css = pelt avalon-tigris = tigris tigris-style = tigris I wasn't sure whether that version info should change or not? --tim Changes: Attachment changed to for-509.patch - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-509?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-509 Here is an overview of the issue: - Key: FOR-509 Summary: Deprecated skin designated to replace non-existant skin Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Maurice Lanselle Created: Fri, 27 May 2005 5:51 AM Updated: Fri, 27 May 2005 9:13 AM Description: In forrest.build.xml, a skin-aliasing occurs to replace skins which no longer exist by an alternative, and a warning is issued. Similarly, a warning is issued when a deprecated skin is chosen. It can happen that a deprecated skin is designated to replace a no-longer-existing skin: this should be avoided to prevent confusion. Maintenance should ensure that only non-deprecated (i.e. supported) skins are designated replacements each time the build file is updated or skins are deprecated. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-507) xml-fop *.xmap files
Message: The following issue has been closed. Resolver: David Crossley Date: Fri, 27 May 2005 8:12 PM Closing, because this was not the problem. - View the issue: http://issues.cocoondev.org//browse/FOR-507 Here is an overview of the issue: - Key: FOR-507 Summary: xml-fop *.xmap files Type: Task Status: Closed Priority: Minor Resolution: WON'T FIX Project: Forrest Components: Other Versions: 0.6 Assignee: Reporter: Clay Leeds Created: Thu, 26 May 2005 11:51 AM Updated: Fri, 27 May 2005 8:12 PM Environment: Mac OS X Description: xml-fop *.xmap files from $FORREST_HOME/context/*.xmap - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
The following comment has been added to this issue: Author: Cyriaque Dupoirieux Created: Thu, 26 May 2005 11:12 AM Body: Excellent, but I don't think it's a minor problem. My own skin - originally based on pelt - is now far from the original one generally for translation reason. The ProjectInfo plugin has now the same limits and I also have my own copy of it... The configuration management begins to be complex for me when a file changes... - View this comment: http://issues.cocoondev.org//browse/FOR-506?page=comments#action_12430 - View the issue: http://issues.cocoondev.org//browse/FOR-506 Here is an overview of the issue: - Key: FOR-506 Summary: Do not hard-code site-visible message strings in skin files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Pedro I. Sanchez Created: Thu, 26 May 2005 10:49 AM Updated: Thu, 26 May 2005 11:12 AM Environment: N/A Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
The following comment has been added to this issue: Author: Ross Gardler Created: Thu, 26 May 2005 11:50 AM Body: Can you describe what you think the problem would be with this propsed solution of extending skinconf.xml? For example: i18n lang=en token name=lastPublished value=Last Published/ token name=copyright value=Copyright/ /i18n i18n lang=?? token name=lastPublished value=???/ token name=copyright value=???/ /i18n This schema allows any token to be added, so customisation of skins would not be a problem. - View this comment: http://issues.cocoondev.org//browse/FOR-506?page=comments#action_12431 - View the issue: http://issues.cocoondev.org//browse/FOR-506 Here is an overview of the issue: - Key: FOR-506 Summary: Do not hard-code site-visible message strings in skin files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Pedro I. Sanchez Created: Thu, 26 May 2005 10:49 AM Updated: Thu, 26 May 2005 11:50 AM Environment: N/A Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-507) xml-fop *.xmap files
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-507 Here is an overview of the issue: - Key: FOR-507 Summary: xml-fop *.xmap files Type: Task Status: Unassigned Priority: Minor Project: Forrest Components: Other Versions: 0.6 Assignee: Reporter: Clay Leeds Created: Thu, 26 May 2005 11:51 AM Updated: Thu, 26 May 2005 11:51 AM Environment: Mac OS X Description: xml-fop *.xmap files from $FORREST_HOME/context/*.xmap - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-507) xml-fop *.xmap files
The following issue has been updated: Updater: Clay Leeds (mailto:[EMAIL PROTECTED]) Date: Thu, 26 May 2005 11:52 AM Comment: *.xmap files from $FORREST_HOME/context/*.xmap to resolve problem of TOC generation for xml-fop FAQ. Changes: Attachment changed to xml-fop-forrest.zip - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-507?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-507 Here is an overview of the issue: - Key: FOR-507 Summary: xml-fop *.xmap files Type: Task Status: Unassigned Priority: Minor Project: Forrest Components: Other Versions: 0.6 Assignee: Reporter: Clay Leeds Created: Thu, 26 May 2005 11:51 AM Updated: Thu, 26 May 2005 11:52 AM Environment: Mac OS X Description: xml-fop *.xmap files from $FORREST_HOME/context/*.xmap - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
The following comment has been added to this issue: Author: Pedro I. Sanchez Created: Thu, 26 May 2005 2:26 PM Body: Couple of comments: 1. It could work, but for me to test it I would like to get clarification on two things: a) How do you enable the i18n .. /i18n thing to work? I just put your code in my web site and Forrest complains with skinconf.xml:369:9: Element type i18n must be declared. skinconf.xml:370:50: Element type token must be declared. b) lang=en, what does it mean? If en refers to the system language in the host where the web developer is working (the locale setting) then this doesn't work. I am developing an all-Spanish web site while working in an all english host environment. 2. What about the non-tokenized strings like Search? - View this comment: http://issues.cocoondev.org//browse/FOR-506?page=comments#action_12433 - View the issue: http://issues.cocoondev.org//browse/FOR-506 Here is an overview of the issue: - Key: FOR-506 Summary: Do not hard-code site-visible message strings in skin files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Pedro I. Sanchez Created: Thu, 26 May 2005 10:49 AM Updated: Thu, 26 May 2005 2:26 PM Environment: N/A Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-506) Do not hard-code site-visible message strings in skin files
The following comment has been added to this issue: Author: Ross Gardler Created: Thu, 26 May 2005 2:48 PM Body: My question was to it was to Cyriaque who said your proposal was not sufficient. I was asking why and adding details to the proposal. But since you ask for more info here we go (if this becomes a desgn discussion we should move it to the dev list and then place a summary here). a) How do you enable the i18n .. /i18n thing to work? I just put your code in my web site and Forrest complains with... My example is intended to be a suggestion for how the DTD could be extended to support what you are requesting. It doesn't exist yet. b) lang=en, what does it mean? Forrest has some in development i18n features, this would be one of them. I'm not sure exactly how it works, but somehow Forrest must be told which language to server. This value would be used in the skinning process in order to select the correct language tokens. 2. What about the non-tokenized strings like Search? Currently none of the strings are tokenised. If we adopt this solution then we will need to tokenise them all. This is open source - can you help us since this is your itch? If you want to tackle this discuss it with us on the dev list, we can help by pointing you in the right direction. Otherwise you'll have to wait until a dev finds the time and inclination to implement this, or another solution. - View this comment: http://issues.cocoondev.org//browse/FOR-506?page=comments#action_12434 - View the issue: http://issues.cocoondev.org//browse/FOR-506 Here is an overview of the issue: - Key: FOR-506 Summary: Do not hard-code site-visible message strings in skin files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.7-dev Assignee: Reporter: Pedro I. Sanchez Created: Thu, 26 May 2005 10:49 AM Updated: Thu, 26 May 2005 2:48 PM Environment: N/A Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-505) Allow the retrieval of raw html files
The following comment has been added to this issue: Author: Ross Gardler Created: Wed, 25 May 2005 8:16 AM Body: See the RT thread at http://marc.theaimsgroup.com/?l=forrest-devm=110145900227224w=2 - View this comment: http://issues.cocoondev.org//browse/FOR-505?page=comments#action_12429 - View the issue: http://issues.cocoondev.org//browse/FOR-505 Here is an overview of the issue: - Key: FOR-505 Summary: Allow the retrieval of raw html files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Tue, 24 May 2005 3:53 PM Updated: Wed, 25 May 2005 8:16 AM Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Assigned: (FOR-500) ensure that all supporting libraries have a corresponding license
Message: The following issue has been re-assigned. Assignee: David Crossley (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Open Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: David Crossley Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Tue, 24 May 2005 3:19 AM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Assigned: (FOR-454) add content about major changes for this release
Message: The following issue has been re-assigned. Assignee: Ross Gardler (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-454 Here is an overview of the issue: - Key: FOR-454 Summary: add content about major changes for this release Type: Task Status: Open Priority: Major Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Tue, 1 Mar 2005 5:15 PM Updated: Tue, 24 May 2005 5:10 AM Description: We need notes about the major changes for this release: upgrading_07.xml announcement-0.7.txt RELEASE-NOTES-0.7.txt - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Assigned: (FOR-470) docs and fresh-site samples for raw content need update
Message: The following issue has been re-assigned. Assignee: Ross Gardler (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-470 Here is an overview of the issue: - Key: FOR-470 Summary: docs and fresh-site samples for raw content need update Type: Task Status: Open Priority: Minor Project: Forrest Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Fri, 18 Mar 2005 7:08 AM Updated: Tue, 24 May 2005 5:11 AM Description: The documentation about raw content describes the method used prior to version 0.7 so we need to update docs and the fresh-site samples. faq.html and upgrading_07.html and elsewhere. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-334) Docbook-Full Plug, Add xml:base to catalog
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 24 May 2005 5:13 AM Plugins are now able to include their own DTD's so I don't think that this is requried any more. If this is not the case please request this issue be reopened and provide the information requested. - View the issue: http://issues.cocoondev.org//browse/FOR-334 Here is an overview of the issue: - Key: FOR-334 Summary: Docbook-Full Plug, Add xml:base to catalog Type: New Feature Status: Closed Priority: Major Resolution: WON'T FIX Project: Forrest Components: Compile Versions: 0.7-dev Assignee: Ross Gardler Reporter: Sean Wheller Created: Tue, 26 Oct 2004 1:41 PM Updated: Tue, 24 May 2005 5:13 AM Description: In XML Catalogs the group/ has @xml:base group xml:base=file:///path/to/forrest/plugins/docbook/resources// I have no way of knowing the path/to/ since I am not in control of the installation. I was wondering if there is a way to add the path/to/ on the pwd during the build. Currently there is no build process for the plugins as they are installed. This is easy to add (please put a feature request into the issue tracker and assign it to me - unless you can do it and submit a patch of course. I should be able to do it later this week). In the meantime, you can hard code it I'll let you know when I've added the build mechanism (it will call an ANT script which can do all the necessary configuration). See this thread in mail-archive http://marc.theaimsgroup.com/?l=forrest-devm=109879620626367w=2 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-378) Enable include or exclude PDF link
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 24 May 2005 5:17 AM This issue is being addressed as part the Views (currently in whiteboard) - View the issue: http://issues.cocoondev.org//browse/FOR-378 Here is an overview of the issue: - Key: FOR-378 Summary: Enable include or exclude PDF link Type: New Feature Status: Closed Priority: Minor Resolution: WON'T FIX Project: Forrest Components: Plugins (general issues) Versions: 0.7-dev Assignee: Ross Gardler Reporter: Sean Wheller Created: Thu, 18 Nov 2004 11:34 AM Updated: Tue, 24 May 2005 5:17 AM Description: Enable PDF plugin to selectively include/exclude documents from PDF transformation and button. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-328) Filesystem Automated Publishing Utility
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Tue, 24 May 2005 5:19 AM Comment: Reduced priority, we are considering an alternative solution to this as a plugin. Not closing the issue as the attached scripts are useful in the meantime. Changes: priority changed from Major to Minor - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-328?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-328 Here is an overview of the issue: - Key: FOR-328 Summary: Filesystem Automated Publishing Utility Type: New Feature Status: Open Priority: Minor Project: Forrest Assignee: Ross Gardler Reporter: Fonzi Created: Thu, 21 Oct 2004 9:56 AM Updated: Tue, 24 May 2005 5:19 AM Environment: OS independent, Ant v. 1.6.x, ant-contrib-1.0b1.jar Description: We have created an utility written in Ant (see attachment) to automatically build a site using forrest. The utility automatically create site.xml and tabs.xml based on the given filesystem path, its structure and content. How we use it: The real first time we run forrest seed as described in http://forrest.apache.org/docs/your-project.html We then make our changes ( in our case we use CVS to check-in our updates and keep the versioning) A periodic build gets called to upload the latest documentation files (from CVS) and run this utility to create site.xml and tabs.xml necessary to run forrest. This way content writers have their work published automatically, a sort of simple automated publishing solution. We find this utility very helpful and hope it is the same for you. Please take into account we have tested the scripts only on a Windows environment using Forrest 0.6 We consider this utility as a starting point for an inspiration as improvements can be done and as well a better integration with Forrest. Credits: The inspiration came from this posting: http://issues.apache.org/eyebrowse/ReadMsg?listId=248msgNo=502 We have also noticed (after we wrote the utility!) some similarities to the libre project: http://forrest.apache.org/docs/libre-intro.html Looking forward to hear your feedback. Fabio del Percio ([EMAIL PROTECTED]) and Bruno Fonzi ([EMAIL PROTECTED]) The package includes: - Build.xml Creates the site.xml and tabs.xml of a forrest site. The build file can be located in any directory as it reads properties from site.properties. It calls createtabs.xml and createsite.xml. - site.properties site.properties is the property file for our build. - createtabs.xml Creates tabs.xml. It creates an Home tab and a new tab for each directory present in the root directory. The root (Home) directory and each of this directories must contain an index.xml file. - createsite.xml Creates the site.xml. It creates an xml tag for each directory present in the root directory. For each of this directories it calls the ant file setSubTags.xml and setSubTagsRecursive.xml. - setSubTags.xml and setSubTagsRecursive.xml They generate links for each file found in the directory, creates a subdir tag for each folder found in the directory and repeat recursively the same task for these directories. setSubTags.xml and setSubTagsRecursive.xml are actually the exact copy of each other. It was necessary to duplicate the two scripts as ANT does not support recursive calls. If anyone has a better solution I would be happy to hear from you. Requirements: Ant v. 1.6.x And ant-contrib-1.0b1.jar http://sourceforge.net/projects/ant-contrib - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-426) Add pod-input plugin to plugins
Message: The following issue has been closed. - View the issue: http://issues.cocoondev.org//browse/FOR-426 Here is an overview of the issue: - Key: FOR-426 Summary: Add pod-input plugin to plugins Type: New Feature Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: Ronald Blaschke Created: Sat, 22 Jan 2005 12:51 PM Updated: Tue, 24 May 2005 5:21 AM Description: Add pod-input plugin to plugins. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-359) Compile error with OpenOffice-Document
Message: The following issue has been closed. - View the issue: http://issues.cocoondev.org//browse/FOR-359 Here is an overview of the issue: - Key: FOR-359 Summary: Compile error with OpenOffice-Document Type: Bug Status: Closed Priority: Minor Resolution: CANNOT REPRODUCE Project: Forrest Versions: 0.7-dev Assignee: Ross Gardler Reporter: Ferdinand Soethe Created: Tue, 9 Nov 2004 9:00 AM Updated: Tue, 24 May 2005 5:21 AM Environment: Windows XP Description: After updating from Forrest 0.6 to yesterdays 0.7 snapshot my openoffice document will not pass the compile runs. The error message is a mystery to me: Failed to create InputSource: file:/C:/Programme/forrest/main/webapp/resources/schema/open-office/dummy.dtd X [0] BookCrossing/bcdownloads.html BROKEN: java.io.FileNotFoundException: P:\forrest\src\documentation\content\xdocs\BookCr ossing\bcdownloads.sxw\office.dtd (Das System kann den angegebenen Pfad nicht finden) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-458) Create a status plugin
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 24 May 2005 1:25 PM The plugin is now fully functional. I've added a note to FOR-217 regarding the FAQ entry. This plugin does not currently solve this problem. - View the issue: http://issues.cocoondev.org//browse/FOR-458 Here is an overview of the issue: - Key: FOR-458 Summary: Create a status plugin Type: New Feature Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: Ross Gardler Created: Thu, 3 Mar 2005 3:19 AM Updated: Tue, 24 May 2005 1:25 PM Description: Extract the pipelines that create changes.xml and todo.xml into a plugin. Expand the status.xml DTD to support the features described in FOR-454 Allow creation of a page from JIRA as described in the user list thread (subject: Pulling issues from Jira issue tracker to use in Forrest, first post 25/2/05) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-217) Certain patterns are claimed by the default sitemaps
The following comment has been added to this issue: Author: Ross Gardler Created: Tue, 24 May 2005 1:25 PM Body: The FAQ Some of my files are not being processed because they use common filenames. needs to be updated when this issue is resolved. - View this comment: http://issues.cocoondev.org//browse/FOR-217?page=comments#action_12422 - View the issue: http://issues.cocoondev.org//browse/FOR-217 Here is an overview of the issue: - Key: FOR-217 Summary: Certain patterns are claimed by the default sitemaps Type: Bug Status: Unassigned Priority: Major Project: Forrest Components: Core operations Fix Fors: 0.9 Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Thu, 15 Jul 2004 3:56 AM Updated: Tue, 24 May 2005 1:25 PM Description: Users are prevented from using certain filenames because those patterns are claimed by the default sitemaps for special processing. These include: site, changes, todo, faq, images, my-images, skinconf, - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-487) generate announcement text from the status.xml
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 24 May 2005 1:29 PM To generate release notes for a particular version request **/release_VERSION_NUMBER.* - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Tue, 24 May 2005 1:29 PM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-503) org.burrokeet.serveletEngine required for eclipse plugin to forrest
The following comment has been added to this issue: Author: Ross Gardler Created: Tue, 24 May 2005 2:52 PM Body: I've proposed moving this code from Burrokeet to here. Since Burrokeet already depends on the Forrest plugin here I do not anticipate any objections. However, I have to wait a couple of days before I am able to actually action the move. - View this comment: http://issues.cocoondev.org//browse/FOR-503?page=comments#action_12425 - View the issue: http://issues.cocoondev.org//browse/FOR-503 Here is an overview of the issue: - Key: FOR-503 Summary: org.burrokeet.serveletEngine required for eclipse plugin to forrest Type: Improvement Status: Open Priority: Blocker Project: Forrest Components: Compile Versions: 0.6 0.7-dev Assignee: Ross Gardler Reporter: Praveen Bhatia Created: Mon, 23 May 2005 8:12 PM Updated: Tue, 24 May 2005 2:52 PM Environment: eclipse 3.* forrest 0.6, 0.7 Description: org.burrokeet.serveletEngine is required for the plugin for eclipse. However, there are no instructions mentioned that needs to be downloaded seperately. Best if it could be bundled with the plugin itself. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-470) docs and fresh-site samples for raw content need update
The following comment has been added to this issue: Author: Ross Gardler Created: Tue, 24 May 2005 3:06 PM Body: What needs to be done: - iHTML is no longer so replace this with a standard HTML page - content on http://localhost:/samples/static.html needs updating as does the location of the example file - content of http://localhost:/samples/linking.html needs updating (I'll get to this tomorrow) - View this comment: http://issues.cocoondev.org//browse/FOR-470?page=comments#action_12426 - View the issue: http://issues.cocoondev.org//browse/FOR-470 Here is an overview of the issue: - Key: FOR-470 Summary: docs and fresh-site samples for raw content need update Type: Task Status: Open Priority: Minor Project: Forrest Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Fri, 18 Mar 2005 7:08 AM Updated: Tue, 24 May 2005 3:06 PM Description: The documentation about raw content describes the method used prior to version 0.7 so we need to update docs and the fresh-site samples. faq.html and upgrading_07.html and elsewhere. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-505) Allow the retrieval of raw html files
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-505 Here is an overview of the issue: - Key: FOR-505 Summary: Allow the retrieval of raw html files Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Tue, 24 May 2005 3:53 PM Updated: Tue, 24 May 2005 3:53 PM Description: 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. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-470) docs and fresh-site samples for raw content need update
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 24 May 2005 4:30 PM Well the wife was busy and the baby was quiet so I fot it done tonight afterall. - View the issue: http://issues.cocoondev.org//browse/FOR-470 Here is an overview of the issue: - Key: FOR-470 Summary: docs and fresh-site samples for raw content need update Type: Task Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: David Crossley Created: Fri, 18 Mar 2005 7:08 AM Updated: Tue, 24 May 2005 4:30 PM Description: The documentation about raw content describes the method used prior to version 0.7 so we need to update docs and the fresh-site samples. faq.html and upgrading_07.html and elsewhere. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-502) Forrest Plugin in eclipse 3.0.2 requires FORREST_HOME path set but it is not handled properly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-502
Here is an overview of the issue:
-
Key: FOR-502
Summary: Forrest Plugin in eclipse 3.0.2 requires FORREST_HOME path set but
it is not handled properly
Type: Bug
Status: Unassigned
Priority: Critical
Project: Forrest
Components:
Tool: Eclipse config
Versions:
0.6
0.7-dev
Assignee:
Reporter: Praveen Bhatia
Created: Mon, 23 May 2005 8:08 PM
Updated: Mon, 23 May 2005 8:08 PM
Environment: eclipse 3.0.2, Forrest 0.7
Description:
I could export the plugin to eclipse. The 'seed' and 'new xdoc' option for the
site menuitem worked. However, Trying, to run the forrest xdoc files in server,
gives error..
First, eclipse forrest plugin asks the preferences for forrest home to be set
for the plugin.
Now if we set c:\forrest as the Forrest Home, it can locate the
forrest.build.xml, but then gives the following error from the server:
CASE 1: If we set FORREST_HOME=C:\forrest in preferences and the FORREST_HOME
variable in cmd shell:
==
C:\forrest\main\forrest.build.xml:63: C:\forrest\main\C:\forrest\lib\core
not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileS
et.java:342)
at org.apache.tools.ant.types.Path.list(Path.java:331)
CASE 2: To avoid the above problem, left the cmd line setting blank.
However, this also gives error. Error when FORREST_HOME is left blank in cmd
shell, but set as c:\forrest in the preferences ==
C:\forrest\main\forrest.build.xml:63:
C:\forrest\main\{$env.FORREST_HOME}\lib\core not found.
at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileS
et.java:342)
at org.apache.tools.ant.types.Path.list(Path.java:331)
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-503) org.burrokeet.serveletEngine required for eclipse plugin to forrest
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-503 Here is an overview of the issue: - Key: FOR-503 Summary: org.burrokeet.serveletEngine required for eclipse plugin to forrest Type: Improvement Status: Unassigned Priority: Blocker Project: Forrest Components: Compile Versions: 0.6 0.7-dev Assignee: Reporter: Praveen Bhatia Created: Mon, 23 May 2005 8:12 PM Updated: Mon, 23 May 2005 8:12 PM Environment: eclipse 3.* forrest 0.6, 0.7 Description: org.burrokeet.serveletEngine is required for the plugin for eclipse. However, there are no instructions mentioned that needs to be downloaded seperately. Best if it could be bundled with the plugin itself. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-95) indirect linking and anchors
The following comment has been added to this issue: Author: David Crossley Created: Sat, 21 May 2005 9:35 PM Body: The Cocoon LinkRewriter Transformer block needs enhancement. http://forrest.apache.org/0.7/docs/sitemap-ref.html#linkrewriting_impl The workaround is to add an entry like this to site.xml to explicitly declare the fragments ... upgrading_07 label=Upgrading to 0.7 href=upgrading_07.html raw href=#raw/ /upgrading_07 and then refer to those as site:upgrading_07 and site:upgrading_07/raw - View this comment: http://issues.cocoondev.org//browse/FOR-95?page=comments#action_12415 - View the issue: http://issues.cocoondev.org//browse/FOR-95 Here is an overview of the issue: - Key: FOR-95 Summary: indirect linking and anchors Type: Improvement Status: Unassigned Priority: Major Project: Forrest Components: Core operations Fix Fors: 0.8 Versions: 0.6 Assignee: Reporter: Richard Cao Created: Thu, 11 Dec 2003 5:43 PM Updated: Sat, 21 May 2005 9:35 PM Description: I would be nice if Forrest supported anchors with indirect linking. That is, something like this: link href=site:somepage#someanchor. (or something similar, like link href=site:somepage anchor=someanchor) If somepage pointed to somepage.html, then the resultant link would be somepage.html#someanchor. Using the above link currently fails with an invalid xpath error since somepage#someanchor is not a valid qname. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-501) Chaperon requiere by core
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-501 Here is an overview of the issue: - Key: FOR-501 Summary: Chaperon requiere by core Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Assignee: Reporter: Juan Jose Pablos Created: Thu, 19 May 2005 7:49 AM Updated: Thu, 19 May 2005 7:49 AM Description: Chaperon seems to be requiered by core. If a chapero-*.jar libray is not in place you will get this error: java.lang.NoClassDefFoundError: net/sourceforge/chaperon/process/LexicalProcessor on sitemap.xmap there is this FIXME: !-- FIXME: there is a bug in the Cocoon 2.2 resolving that can make cocoon:/ calls call the base sitemap; remove the following when it's fixed. -- It needs more investigation as it seems to fail only using Command line and not when running as servlet - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-501) Chaperon requiere by core
The following issue has been updated: Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) Date: Thu, 19 May 2005 7:51 AM Changes: Fix Version changed to 0.8 - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-501?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-501 Here is an overview of the issue: - Key: FOR-501 Summary: Chaperon requiere by core Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Fix Fors: 0.8 Assignee: Reporter: Juan Jose Pablos Created: Thu, 19 May 2005 7:49 AM Updated: Thu, 19 May 2005 7:51 AM Description: Chaperon seems to be requiered by core. If a chapero-*.jar libray is not in place you will get this error: java.lang.NoClassDefFoundError: net/sourceforge/chaperon/process/LexicalProcessor on sitemap.xmap there is this FIXME: !-- FIXME: there is a bug in the Cocoon 2.2 resolving that can make cocoon:/ calls call the base sitemap; remove the following when it's fixed. -- It needs more investigation as it seems to fail only using Command line and not when running as servlet - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-501) Chaperon requiere by core
The following issue has been updated: Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) Date: Thu, 19 May 2005 7:50 AM Comment: This patch resolved the problem as it removes a dinamic generation of gramars.. Changes: Attachment changed to chaperon-dependency-core.diff - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-501?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-501 Here is an overview of the issue: - Key: FOR-501 Summary: Chaperon requiere by core Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Fix Fors: 0.8 Assignee: Reporter: Juan Jose Pablos Created: Thu, 19 May 2005 7:49 AM Updated: Thu, 19 May 2005 7:50 AM Description: Chaperon seems to be requiered by core. If a chapero-*.jar libray is not in place you will get this error: java.lang.NoClassDefFoundError: net/sourceforge/chaperon/process/LexicalProcessor on sitemap.xmap there is this FIXME: !-- FIXME: there is a bug in the Cocoon 2.2 resolving that can make cocoon:/ calls call the base sitemap; remove the following when it's fixed. -- It needs more investigation as it seems to fail only using Command line and not when running as servlet - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-500) ensure that all supporting libraries have a corresponding license
The following comment has been added to this issue: Author: Juan Jose Pablos Created: Wed, 18 May 2005 5:41 PM Body: I have added a few, but I am not able to find these ones: commons-jci-r159148.jar excalibur-pool-api-2.0.0.jar excalibur-pool-impl-2.0.0.jar excalibur-pool-instrumented-2.0.0.jar and I am not sure about this: oreilly.codepolicy.txt oreilly.permission.txt w3c-dtd-license.txt - View this comment: http://issues.cocoondev.org//browse/FOR-500?page=comments#action_12407 - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Wed, 18 May 2005 5:41 PM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-336) Table alignment problem with pelt and IE
The following comment has been added to this issue: Author: Addison Berry Created: Wed, 18 May 2005 7:37 PM Body: It looks like it has to do with the table being 100% (#content table in basics.css). I switched it to 99% to see and that eleiminates the problem of dropping it below the menu, but then, of course the table is only 99%. I'm sure it is IE being stupid and I'm sure there is a fix out there. I'll see if I can track down the IE hack to correct this. - View this comment: http://issues.cocoondev.org//browse/FOR-336?page=comments#action_12408 - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 7:37 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-336) Table alignment problem with pelt and IE
The following issue has been updated: Updater: Addison Berry (mailto:[EMAIL PROTECTED]) Date: Wed, 18 May 2005 7:40 PM Comment: This is a page with the table set to 99%. Changes: Attachment changed to screenshot-ie99.jpg - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-336?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Skins (general issues) Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 7:40 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-500) ensure that all supporting libraries have a corresponding license
The following comment has been added to this issue: Author: David Crossley Created: Wed, 18 May 2005 8:21 PM Body: The orielly.* and W3C DTD ones are okay as is (see the mail archives). Found the excalibur pool license at archive.apache.org Found the commons-jci at Jakarta Commons in sandbox. - View this comment: http://issues.cocoondev.org//browse/FOR-500?page=comments#action_12410 - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Wed, 18 May 2005 8:21 PM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-336) Table alignment problem with pelt and IE
The following comment has been added to this issue:
Author: Addison Berry
Created: Wed, 18 May 2005 9:24 PM
Body:
Ok, this is simpler and hides from Moz properly.
#content table {
border: 0;
width: 100%;
}
/*Hack to get IE to render the table at 100%*/
* html #content table { margin-left: -3px; }
-
View this comment:
http://issues.cocoondev.org//browse/FOR-336?page=comments#action_12412
-
View the issue:
http://issues.cocoondev.org//browse/FOR-336
Here is an overview of the issue:
-
Key: FOR-336
Summary: Table alignment problem with pelt and IE
Type: Bug
Status: Unassigned
Priority: Minor
Project: Forrest
Components:
Skins (general issues)
Versions:
0.6
0.7-dev
Assignee:
Reporter: Stefano Mancarella
Created: Wed, 27 Oct 2004 8:51 AM
Updated: Wed, 18 May 2005 9:24 PM
Environment: Forrest 0.6
Internet Explorer 6.0
Description:
There's a strange (css?) problem using tables with the pelt skin and viewing
the result in IE.
If a page contains a table, the table itself always starts below the menu in IE.
So if the table is among the first elements of the page and the menu is long,
the result is a blank space before the table itself.
To reproduce the problem do a forrest seed, add a table to index.xml (just
below the body tag) and see the result in IE.
The problem doesn't show up in browsers of the Mozilla family, so maybe it's
due to a bug in IE.
Tested with both 0.6 and trunk.
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-336) Table alignment problem with pelt and IE
Message: The following issue has been closed. Resolver: David Crossley Date: Wed, 18 May 2005 10:06 PM Addison, thanks for your contribution. Your tweak is now added to the trunk (i.e. 0.7-dev). - View the issue: http://issues.cocoondev.org//browse/FOR-336 Here is an overview of the issue: - Key: FOR-336 Summary: Table alignment problem with pelt and IE Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Skins (general issues) Fix Fors: 0.7-dev Versions: 0.6 0.7-dev Assignee: Reporter: Stefano Mancarella Created: Wed, 27 Oct 2004 8:51 AM Updated: Wed, 18 May 2005 10:06 PM Environment: Forrest 0.6 Internet Explorer 6.0 Description: There's a strange (css?) problem using tables with the pelt skin and viewing the result in IE. If a page contains a table, the table itself always starts below the menu in IE. So if the table is among the first elements of the page and the menu is long, the result is a blank space before the table itself. To reproduce the problem do a forrest seed, add a table to index.xml (just below the body tag) and see the result in IE. The problem doesn't show up in browsers of the Mozilla family, so maybe it's due to a bug in IE. Tested with both 0.6 and trunk. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-497) Cannot use http in navigation menu
Message: The following issue has been closed. Resolver: Ross Gardler Date: Tue, 17 May 2005 6:23 AM My mistake, the broken link was actually in tabs.xml and it was because I was using dir instead of href to specify the link destination. - View the issue: http://issues.cocoondev.org//browse/FOR-497 Here is an overview of the issue: - Key: FOR-497 Summary: Cannot use http in navigation menu Type: Bug Status: Closed Priority: Major Resolution: WON'T FIX Project: Forrest Fix Fors: 0.7-dev Versions: 0.8 Assignee: Reporter: Ross Gardler Created: Tue, 17 May 2005 6:19 AM Updated: Tue, 17 May 2005 6:23 AM Description: If site.xml contains a reference to an external link via an http: link the generation of th site fails: broken-links link message=No pipeline matched request: http:/forrest.apache.org/docs/plug ins/index.xml uri=http:/forrest.apache.org/docs/plugins/index.html referrer uri=linkmap.html/ referrer uri=samples/openoffice-writer-howto.html/ referrer uri=samples/index.html/ referrer uri=changes.html/ referrer uri=index.html/ referrer uri=todo.html/ referrer uri=samples/openoffice-writer.html/ referrer uri=samples/openoffice-impress.html/ /link /broken-links - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-499) Modiications to the Eclipse Plugin for Forrest
The following issue has been updated: Updater: Anil Ramnanan (mailto:[EMAIL PROTECTED]) Date: Tue, 17 May 2005 9:45 AM Changes: Attachment changed to forrestPatch.txt - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-499?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-499 Here is an overview of the issue: - Key: FOR-499 Summary: Modiications to the Eclipse Plugin for Forrest Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Tool: Eclipse config Versions: 0.7-dev Assignee: Reporter: Anil Ramnanan Created: Tue, 17 May 2005 9:44 AM Updated: Tue, 17 May 2005 9:45 AM Description: This patch includes two fixes: 1. It prevents the user from starting more than one instance of the live server 2. It waits until the server is loaded before it opens the web browser. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-496) Cannot put a link on an image
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-496 Here is an overview of the issue: - Key: FOR-496 Summary: Cannot put a link on an image Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: OpenOffice.org Versions: 0.7-dev Assignee: Reporter: Cyriaque Dupoirieux Created: Tue, 17 May 2005 2:41 AM Updated: Tue, 17 May 2005 2:41 AM Environment: Any Description: Links under images in sxw sources are ignored in the resulting XHTML. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-394) html2document.xsl misses content before first h1 element
The following comment has been added to this issue: Author: Juan Jose Pablos Created: Tue, 17 May 2005 12:16 PM Body: the problem is is actually on these lines: !--infer structure from sibling headings-- xsl:template match=body body xsl:choose xsl:when test=h1 xsl:call-template name=process_h1/ /xsl:when xsl:otherwise section xsl:if test=a/@name xsl:attribute name=idxsl:value-of select=a/@name//xsl:attribute /xsl:if title/ xsl:apply-templates/ xsl:call-template name=process_h1/ /section /xsl:otherwise /xsl:choose /body /xsl:template - View this comment: http://issues.cocoondev.org//browse/FOR-394?page=comments#action_12397 - View the issue: http://issues.cocoondev.org//browse/FOR-394 Here is an overview of the issue: - Key: FOR-394 Summary: html2document.xsl misses content before first h1 element Type: Bug Status: Unassigned Priority: Minor Project: Forrest Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Thu, 25 Nov 2004 7:22 PM Updated: Tue, 17 May 2005 12:16 PM Description: The html2document.xsl stylesheet does not transform content that precedes the first H1 element. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-153) Removing unneed Jar on forrest distribution.
The following comment has been added to this issue: Author: Ross Gardler Created: Tue, 17 May 2005 12:31 PM Body: This is a useful analysis. Plugins can now have jar files in their lib directory, so for those needed by plugins only it should be a case of moving those out of core. --- The neko* jars are used to generate the DTD dcumentation, this funcitonlaity has been moved to a plugin as well. - View this comment: http://issues.cocoondev.org//browse/FOR-153?page=comments#action_12398 - View the issue: http://issues.cocoondev.org//browse/FOR-153 Here is an overview of the issue: - Key: FOR-153 Summary: Removing unneed Jar on forrest distribution. Type: Task Status: Open Priority: Major Project: Forrest Components: Compile Assignee: Juan Jose Pablos Reporter: Juan Jose Pablos Created: Thu, 27 May 2004 11:18 AM Updated: Tue, 17 May 2005 12:31 PM Description: There are 71 Jar on our distribution. I am not 100% sure that all these jar are needed. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-441) build patch doesn't work
Message:
The following issue has been closed.
Resolver: Juan Jose Pablos
Date: Tue, 17 May 2005 12:11 PM
missins dependecy to init so forrest.home was unknow for that target
-
View the issue:
http://issues.cocoondev.org//browse/FOR-441
Here is an overview of the issue:
-
Key: FOR-441
Summary: build patch doesn't work
Type: Bug
Status: Closed
Priority: Minor
Resolution: FIXED
Project: Forrest
Versions:
0.7-dev
Assignee:
Reporter: Johannes Schaefer
Created: Mon, 21 Feb 2005 5:18 AM
Updated: Tue, 17 May 2005 12:11 PM
Environment: Win XP, C:\j2sdk1.4.2_04, forrrest r. 154668
Description:
'build patch' doesn't work.
H:\forrest154656-0221svn status
? plugins\org.apache.forrest.plugin.excel\resources
! plugins\org.apache.forrest.plugin.excel\src\documentation\resources
H:\forrest154656-0221cd main
H:\forrest154656-0221\mainbuild patch
Using classpath:
;..\lib\endorsed\jakarta-bcel-20040329.jar;..\lib\endorsed\jakarta-regexp-1.3.jar;..\lib\endorsed\xala
n-2.6.1-dev-20041008T0304.jar;..\lib\endorsed\xercesImpl-2.6.2.jar;..\lib\endorsed\xml-apis.jar
Buildfile: build.xml
BUILD FAILED
H:\forrest154656-0221\main\build.xml:389: The following error occurred while
executing this line:
java.io.FileNotFoundException:
H:\forrest154656-0221\main\${forrest.home}\tools\targets\patch.xml (Das System
kann den a
ngegebenen Pfad nicht finden)
Total time: 0 seconds
-
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.cocoondev.org//secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-153) Removing unneed Jar on forrest distribution.
The following comment has been added to this issue: Author: Juan Jose Pablos Created: Tue, 17 May 2005 12:57 PM Body: ok. I wanted to say that I was not sure if that funcionality was needed anymore. Moved neko*.jar and xerces-xniWriter.jar to plugins/org.apache.forrest.plugin.input.dtdx/lib/ - View this comment: http://issues.cocoondev.org//browse/FOR-153?page=comments#action_12399 - View the issue: http://issues.cocoondev.org//browse/FOR-153 Here is an overview of the issue: - Key: FOR-153 Summary: Removing unneed Jar on forrest distribution. Type: Task Status: Open Priority: Major Project: Forrest Components: Compile Assignee: Juan Jose Pablos Reporter: Juan Jose Pablos Created: Thu, 27 May 2004 11:18 AM Updated: Tue, 17 May 2005 12:57 PM Description: There are 71 Jar on our distribution. I am not 100% sure that all these jar are needed. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-259) openoffice files can skip sections
The following comment has been added to this issue: Author: Ferdinand Soethe Created: Tue, 17 May 2005 1:47 PM Body: Heading 4 Heading 9 Heading 2 I suggest to clearly flag Heading 9 as a layering error. If it was not ommitted and would have been translated it would create invalid HTML (even in HTML you must not skip heading levels when going down the hierarchy) and possibly create validity problems in 0.8 and XHTML. - View this comment: http://issues.cocoondev.org//browse/FOR-259?page=comments#action_12401 - View the issue: http://issues.cocoondev.org//browse/FOR-259 Here is an overview of the issue: - Key: FOR-259 Summary: openoffice files can skip sections Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: OpenOffice.org Fix Fors: 0.8 Versions: 0.6 Assignee: Reporter: Dave Brondsema Created: Wed, 18 Aug 2004 2:32 AM Updated: Tue, 17 May 2005 1:47 PM Description: Create an openoffice file with lines like this: Heading 2 Heading 3 Heading 4 Heading 9 Heading 2 The last two lines are not translated into sections. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-498) colspan not respected by Text plugin
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-498 Here is an overview of the issue: - Key: FOR-498 Summary: colspan not respected by Text plugin Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugins (general issues) Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Tue, 17 May 2005 8:58 AM Updated: Tue, 17 May 2005 8:58 AM Description: If a table element has a colspan attribute the text plugin ignores it. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Assigned: (FOR-153) Removing unneed Jar on forrest distribution.
Message: The following issue has been re-assigned. Assignee: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-153 Here is an overview of the issue: - Key: FOR-153 Summary: Removing unneed Jar on forrest distribution. Type: Task Status: Open Priority: Major Project: Forrest Components: Compile Assignee: Juan Jose Pablos Reporter: Juan Jose Pablos Created: Thu, 27 May 2004 11:18 AM Updated: Tue, 17 May 2005 8:20 AM Description: There are 71 Jar on our distribution. I am not 100% sure that all these jar are needed. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-495) Problem with Cocoon cache when regenerating
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-495 Here is an overview of the issue: - Key: FOR-495 Summary: Problem with Cocoon cache when regenerating Type: Bug Status: Unassigned Priority: Major Project: Forrest Components: Plugin: OpenOffice.org Versions: 0.7-dev Assignee: Reporter: Cyriaque Dupoirieux Created: Tue, 17 May 2005 2:40 AM Updated: Tue, 17 May 2005 2:40 AM Environment: Any Description: Modification of sxw sources are not taken into account if you do not delete the cocoon cache. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-500) ensure that all supporting libraries have a corresponding license
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-500 Here is an overview of the issue: - Key: FOR-500 Summary: ensure that all supporting libraries have a corresponding license Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 17 May 2005 7:25 PM Updated: Tue, 17 May 2005 7:25 PM Description: Some old libraries and some of the recently updated libraries do not have an updated license file. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-153) Removing unneed Jar on forrest distribution.
The following comment has been added to this issue: Author: David Crossley Created: Tue, 17 May 2005 7:59 PM Body: Eeek, please do testing after each jar move. cd main ./build.sh clean ./build.sh ... Compiling 31 source files to /svn/asf/forrest/build/classes /svn/asf/forrest/main/java/org/apache/forrest/sourcetype/SourceTypeAction.java:19: package org.cyberneko.pull does not exist import org.cyberneko.pull.XMLPullParser; ... - View this comment: http://issues.cocoondev.org//browse/FOR-153?page=comments#action_12405 - View the issue: http://issues.cocoondev.org//browse/FOR-153 Here is an overview of the issue: - Key: FOR-153 Summary: Removing unneed Jar on forrest distribution. Type: Task Status: Open Priority: Major Project: Forrest Components: Compile Assignee: Juan Jose Pablos Reporter: Juan Jose Pablos Created: Thu, 27 May 2004 11:18 AM Updated: Tue, 17 May 2005 7:59 PM Description: There are 71 Jar on our distribution. I am not 100% sure that all these jar are needed. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-494) Links not rendered correctly in text output plugin
Message: The following issue has been closed. Resolver: Rick Tessner Date: Tue, 17 May 2005 9:58 PM Fix this. The icon, img and acronym elements had the same issue, so fixed them as well. This plugin has also been successfully deployed, so I'm closing this issue. - View the issue: http://issues.cocoondev.org//browse/FOR-494 Here is an overview of the issue: - Key: FOR-494 Summary: Links not rendered correctly in text output plugin Type: Bug Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 13 May 2005 5:01 PM Updated: Tue, 17 May 2005 9:58 PM Description: Links in list items are not rendered by the text output plugin Also, there is no space between a link and the following text - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-494) Links not rendered correctly in text output plugin
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-494 Here is an overview of the issue: - Key: FOR-494 Summary: Links not rendered correctly in text output plugin Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugins (general issues) Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 13 May 2005 5:01 PM Updated: Fri, 13 May 2005 5:01 PM Description: Links in list items are not rendered by the text output plugin Also, there is no space between a link and the following text - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-227) static html site: index.html missing in links
Message: The following issue has been closed. Resolver: Ross Gardler Date: Thu, 12 May 2005 8:42 PM The missing links issue is now in the FAQ: http://forrest.apache.org/0.7/docs/faq.html#defaultStartPage I've not applied the breadcrumbs patch as it assumes that the page referred to is a index.html and we cannot make this assumption. instead I have added a comment to skinconf.xml pointing out the breadcrumb href must point to a file. - View the issue: http://issues.cocoondev.org//browse/FOR-227 Here is an overview of the issue: - Key: FOR-227 Summary: static html site: index.html missing in links Type: Bug Status: Closed Priority: Minor Resolution: WON'T FIX Project: Forrest Fix Fors: 0.7-dev Versions: 0.6 Assignee: Ross Gardler Reporter: Johannes Schaefer Created: Thu, 22 Jul 2004 5:10 PM Updated: Thu, 12 May 2005 8:42 PM Environment: any Description: When creating a static html site (running command forrest) links in the document that point to a directory (index.html) are broken when using the site without a server (file://) To fix: add the filename to the links, i.e. create a href=../chapter1/index.html instead of a href=../chapter1/ - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-391) website docs/site split
The following comment has been added to this issue: Author: David Crossley Created: Tue, 10 May 2005 11:42 PM Body: Another thread: Forrest sites google ranking http://marc.theaimsgroup.com/?t=11153051114 in which we solved the issues with redirecting to the relevant docs. Now we have an 'svn co' of the release docs at the top-level and the .htaccess just handles some particular situations. - View this comment: http://issues.cocoondev.org//browse/FOR-391?page=comments#action_12378 - View the issue: http://issues.cocoondev.org//browse/FOR-391 Here is an overview of the issue: - Key: FOR-391 Summary: website docs/site split Type: Task Status: Open Priority: Major Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: David Crossley Reporter: Dave Brondsema Created: Wed, 24 Nov 2004 10:51 PM Updated: Tue, 10 May 2005 11:42 PM Description: Split our website into a standalone documentation site (which will be maintained per version/branch) and the main version-independent site. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-229) some SVG not converted to PNG, while other SVG are okay (DOCTYPE issue?)
The following issue has been updated: Updater: David Crossley (mailto:[EMAIL PROTECTED]) Date: Wed, 11 May 2005 12:28 AM Changes: summary changed from SVG not converted to PNG to some SVG not converted to PNG, while other SVG are okay (DOCTYPE issue?) Version changed to 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-229?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-229 Here is an overview of the issue: - Key: FOR-229 Summary: some SVG not converted to PNG, while other SVG are okay (DOCTYPE issue?) Type: Bug Status: Unassigned Priority: Major Project: Forrest Components: Core operations Fix Fors: 0.7-dev Versions: 0.6 0.7-dev Assignee: Reporter: Dave Brondsema Created: Mon, 26 Jul 2004 2:45 PM Updated: Wed, 11 May 2005 12:28 AM Description: See http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]by=threadfrom=828955 - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Assigned: (FOR-487) generate announcement text from the status.xml
Message: The following issue has been re-assigned. Assignee: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Open Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Juan Jose Pablos Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Mon, 9 May 2005 3:41 AM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-487) generate announcement text from the status.xml
The following issue has been updated: Updater: Juan Jose Pablos (mailto:[EMAIL PROTECTED]) Date: Mon, 9 May 2005 3:43 AM Comment: dtd changed needed Changes: Attachment changed to importance.patch - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-487?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Open Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Juan Jose Pablos Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Mon, 9 May 2005 3:43 AM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-493) site: protocol fails in tabs
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-493 Here is an overview of the issue: - Key: FOR-493 Summary: site: protocol fails in tabs Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Sat, 7 May 2005 3:55 AM Updated: Sat, 7 May 2005 3:55 AM Description: Whilst it is legal to have an external link in tabs this canot be achieved with the site: protocol. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-492) Inconsitent Line Endings in generated sites
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-492 Here is an overview of the issue: - Key: FOR-492 Summary: Inconsitent Line Endings in generated sites Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 6 May 2005 10:04 AM Updated: Fri, 6 May 2005 10:04 AM Environment: Windows (with or without CYGWIN) Description: Sites generated by Forrest have inconsitent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce cd into any plugin directory, do ant docs and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-492) Inconsistent Line Endings in generated sites
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Fri, 6 May 2005 10:07 AM Changes: summary changed from Inconsitent Line Endings in generated sites to Inconsistent Line Endings in generated sites description changed from Sites generated by Forrest have inconsitent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce cd into any plugin directory, do ant docs and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? to Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? Fix Version changed to 0.8 - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-492?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-492 Here is an overview of the issue: - Key: FOR-492 Summary: Inconsistent Line Endings in generated sites Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Core operations Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Fri, 6 May 2005 10:04 AM Updated: Fri, 6 May 2005 10:07 AM Environment: Windows (with or without CYGWIN) Description: Sites generated by Forrest have inconsistent line endings when created on a Windows platform. I did a little testing, here's what I have discovered so far: - any file that is processed by XSLT has the line endings problem - on investigating one such file (index.html) I discovered that the generated comments from site2xhtml.xsl (such as breadtrail comment) have CRLF endings whilst most other lines have LF endings. I'm running on Windows, and get the same results whether I run under CYGWIN or DOS. To reproduce run forrest site in any site and check out the generated docs in build/site. This appears to a result of the XSLT transformations. xsl:comments retain the line endings contained in the XSL file, whilst other line endings are set to the environment default. Is there a way to tell the XSLT transformer what line endings to use? - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-489) initial run of forrest from dist fails
The following comment has been added to this issue: Author: David Crossley Created: Thu, 5 May 2005 1:17 AM Body: It is important that this issue gets solved. You will get other problems if you don't use Forrest's packaged Ant. This sounds like the same type of issue that was fixed by http://issues.cocoondev.org/browse/FOR-471 David, please try the change that was suggested there. - View this comment: http://issues.cocoondev.org//browse/FOR-489?page=comments#action_12352 - View the issue: http://issues.cocoondev.org//browse/FOR-489 Here is an overview of the issue: - Key: FOR-489 Summary: initial run of forrest from dist fails Type: Bug Status: Unassigned Priority: Critical Project: Forrest Components: Launch 'forrest' Versions: 0.6 Assignee: Reporter: David Jung Created: Fri, 29 Apr 2005 11:32 AM Updated: Thu, 5 May 2005 1:17 AM Environment: Redhat Fedora Core 3, Sun JDK 1.5.0-b64 Description: Initial run of forrest per install instructions failed (first time user). Downloaded and untarred 0.6 dist. set env var FORREST_HOME in bash added FORREST_HOME/bin to path. cd'd into top-level and entered 'forrest' on cmd line Result was this: Apache Forrest. Run 'forrest -projecthelp' to list options /usr/bin/build-classpath: error: could not find ant-launcher Java extension for this JVM /usr/bin/build-classpath: error: All specified jars were not found I downloaded and tried an Apr28 snapshot with similar results. (it complained it needed to be built first. Running the build script gave the same error as above) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-262) openoffice2forrest: add support for merged cells in tables
Message: The following issue has been closed. Resolver: Ross Gardler Date: Thu, 5 May 2005 4:31 AM Reapplied - thanks Charles (sorry it took so long to reapply this) - View the issue: http://issues.cocoondev.org//browse/FOR-262 Here is an overview of the issue: - Key: FOR-262 Summary: openoffice2forrest: add support for merged cells in tables Type: Improvement Status: Closed Priority: Major Resolution: FIXED Project: Forrest Components: Plugin: OpenOffice.org Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: Charles Palmer Created: Sun, 22 Aug 2004 1:06 PM Updated: Thu, 5 May 2005 4:31 AM Description: Processing of OpenOffice files is useful, but tables containing merged cells are not handled properly, preventing the use of many OpenOffice documents with Forrest. If you merge two cells in OOo you get this attribute: table:number-columns-spanned=2 and this could translate into the HTML colspan=2 attribute. But it's not happening - does this first require an enhancement of the Forrest DTD? Which seems to contain the following: !ENTITY % cell.span 'colspan CDATA 1 rowspan CDATA 1' and !ATTLIST td %common.att; %cell.span; Does this prevent cells from spanning rows and columns? - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-394) html2document.xsl misses content before first h1 element
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Thu, 5 May 2005 4:47 AM Changes: Fix Version changed to 0.8 Fix Version changed from 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-394?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-394 Here is an overview of the issue: - Key: FOR-394 Summary: html2document.xsl misses content before first h1 element Type: Bug Status: Unassigned Priority: Minor Project: Forrest Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Thu, 25 Nov 2004 7:22 PM Updated: Thu, 5 May 2005 4:47 AM Description: The html2document.xsl stylesheet does not transform content that precedes the first H1 element. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-433) OpenOffice.org plugin produces invalid intermediate documents
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Thu, 5 May 2005 4:48 AM Comment: This issue has a workaround in place, some more work is required though. Changes: Fix Version changed to 0.8 Fix Version changed from 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-433?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-433 Here is an overview of the issue: - Key: FOR-433 Summary: OpenOffice.org plugin produces invalid intermediate documents Type: Improvement Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: OpenOffice.org Fix Fors: 0.8 Versions: 0.8 Assignee: Reporter: Florian G. Haas Created: Fri, 4 Feb 2005 4:06 PM Updated: Thu, 5 May 2005 4:48 AM Environment: Tested on Debian Sarge with Linux 2.4.27 an JDK 1.4.2 Description: The intermediate XML produced by the OOo plugin does not conform to the document-v12 DTD, even though the xsl:output element in openoffice-common2forrest.xsl says so. In particular: * The intermediate document contains a style element inside header; invalid per the DTD. * p elements contain a class attribute; invalid per the DTD. * fixme elements do not contain an author attribute, though required by the DTD. Steps to reproduce: * Run forrest run from the plugins/org.apache.forrest.plugin.OpenOffice.org subdirectory of your Forrest checkout. * Download http://localhost:/samples/openoffice-writer.xml and have the document checked by your favorite validating parser. The trouble with this is that the FO stylesheets carry the contents of the style element over into the result tree, where they pop up as part of the ToC. This looks like fairly meaningless gibberish to the reader of the resulting PDF (etc.) document. You may verify this by checking http://localhost:/samples/openoffice-writer.pdf in the above-mentioned setup. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-341) Plugin resources are not copied to site
The following issue has been updated: Updater: Ross Gardler (mailto:[EMAIL PROTECTED]) Date: Thu, 5 May 2005 4:50 AM Comment: This is happening in the S5 plugin because there are JS scripts that are imported by linked JS scripts. That is, Forrest has no way of knowing they are there. Since this only affects one plugin, and that plugin is not a part of the Forrest project, but a third party effort (with me being the third party), this can be pushed to 0.8 Changes: description changed from If a plugin contains some resources required in a statically built site (such as Javascripts) they are not copied across to build/site when forrest site is run to If a plugin contains some resources required in a statically built site (such as Javascripts) they are not copied across to build/site when forrest site is run. Fix Version changed to 0.8 Fix Version changed from 0.7-dev - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-341?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-341 Here is an overview of the issue: - Key: FOR-341 Summary: Plugin resources are not copied to site Type: Bug Status: Open Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Ross Gardler Reporter: Ross Gardler Created: Sat, 30 Oct 2004 7:16 PM Updated: Thu, 5 May 2005 4:50 AM Description: If a plugin contains some resources required in a statically built site (such as Javascripts) they are not copied across to build/site when forrest site is run. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-259) openoffice files can skip sections
The following comment has been added to this issue: Author: Ross Gardler Created: Thu, 5 May 2005 4:51 AM Body: The comments imply this issue has been fixed. Can we close it? - View this comment: http://issues.cocoondev.org//browse/FOR-259?page=comments#action_12357 - View the issue: http://issues.cocoondev.org//browse/FOR-259 Here is an overview of the issue: - Key: FOR-259 Summary: openoffice files can skip sections Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Plugin: OpenOffice.org Fix Fors: 0.7-dev Versions: 0.6 Assignee: Reporter: Dave Brondsema Created: Wed, 18 Aug 2004 2:32 AM Updated: Thu, 5 May 2005 4:51 AM Description: Create an openoffice file with lines like this: Heading 2 Heading 3 Heading 4 Heading 9 Heading 2 The last two lines are not translated into sections. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-416) input/output formats documented
Message: The following issue has been closed. Resolver: Ross Gardler Date: Thu, 5 May 2005 10:16 AM There is an up-to-date index file at http://forrest.apache.org/0.7/docs/plugins/index.html This will be automatically generated and updated when a plugin is deployed (new buildfile not yet committed due to some problems with plugin docs, however this is another issue on the tracker so closing this one). - View the issue: http://issues.cocoondev.org//browse/FOR-416 Here is an overview of the issue: - Key: FOR-416 Summary: input/output formats documented Type: Task Status: Closed Priority: Major Resolution: FIXED Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: Dave Brondsema Created: Thu, 6 Jan 2005 6:04 PM Updated: Thu, 5 May 2005 10:16 AM Description: Clearly document all possible input and output formats, and any advantages and disadvantages of them. IMHO, I envision this as a new, short page, rather than letting it get lost in any existing page (although it would be good also to modifying the front page's quick steps and Using Forrest to show there are more options than XML for source). - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-340) plugin build file
Message: The following issue has been closed. - View the issue: http://issues.cocoondev.org//browse/FOR-340 Here is an overview of the issue: - Key: FOR-340 Summary: plugin build file Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Project: Forrest Components: Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Ross Gardler Reporter: Ross Gardler Created: Sat, 30 Oct 2004 7:05 PM Updated: Thu, 5 May 2005 6:48 PM Description: A build file is required to aid the management of plugins, this build file should: - build the distribution version of one or more plugins - update the plugins.xml file in forrestcore - upload plugin distributions to their distribution server - build the plugin documentation - upload the plugin documentation to its web space - upload the src documentation to the repository location - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-491) Dead link in http://forrest.apache.org/0.7/docs/index.html
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-491 Here is an overview of the issue: - Key: FOR-491 Summary: Dead link in http://forrest.apache.org/0.7/docs/index.html Type: Bug Status: Unassigned Priority: Minor Project: Forrest Components: Documentation and website Assignee: Reporter: Ferdinand Soethe Created: Wed, 4 May 2005 2:13 AM Updated: Wed, 4 May 2005 2:13 AM Description: Link http://forrest.apache.org/0.8/ in (menu documentation other versions - 0.8) http://forrest.apache.org/0.7/docs/index.html is currently dead. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Created: (FOR-490) serve multiple sites on a single Forrest instance
Message: A new issue has been created in JIRA. - View the issue: http://issues.cocoondev.org//browse/FOR-490 Here is an overview of the issue: - Key: FOR-490 Summary: serve multiple sites on a single Forrest instance Type: New Feature Status: Unassigned Priority: Major Project: Forrest Components: Core operations Fix Fors: 0.8 Versions: 0.8 Assignee: Reporter: Johannes Schaefer Created: Tue, 3 May 2005 2:06 AM Updated: Tue, 3 May 2005 2:06 AM Description: Nicola Ken Barozzi wrote: After that, it would be beneficial to be able to serve multiple sites on a single Forrest instance, so that we can have other projects join and have their site served. This last point (seving multiple sites from one Forrest instance) is important even without moving Forrest to a live server (I'm +1 on this). Right now we have various styleguides in Forrest and if I need to run them at once I have to start Forrest/jetty with different ports. (From Thread [RT] Serving Apache Forrest site from live Forrest on dev-list. Will add link later.) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-490) serve multiple sites on a single Forrest instance
The following comment has been added to this issue: Author: Johannes Schaefer Created: Tue, 3 May 2005 3:28 AM Body: Here's the link to the Mail: http://marc.theaimsgroup.com/?l=forrest-devm=111510406905741w=2 - View this comment: http://issues.cocoondev.org//browse/FOR-490?page=comments#action_12335 - View the issue: http://issues.cocoondev.org//browse/FOR-490 Here is an overview of the issue: - Key: FOR-490 Summary: serve multiple sites on a single Forrest instance Type: New Feature Status: Unassigned Priority: Major Project: Forrest Components: Core operations Fix Fors: 0.8 Versions: 0.8 Assignee: Reporter: Johannes Schaefer Created: Tue, 3 May 2005 2:06 AM Updated: Tue, 3 May 2005 3:28 AM Description: Nicola Ken Barozzi wrote: After that, it would be beneficial to be able to serve multiple sites on a single Forrest instance, so that we can have other projects join and have their site served. This last point (seving multiple sites from one Forrest instance) is important even without moving Forrest to a live server (I'm +1 on this). Right now we have various styleguides in Forrest and if I need to run them at once I have to start Forrest/jetty with different ports. (From Thread [RT] Serving Apache Forrest site from live Forrest on dev-list. Will add link later.) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-487) generate announcement text from the status.xml
The following comment has been added to this issue: Author: Juan Jose Pablos Created: Mon, 2 May 2005 5:43 PM Body: What about using impact or importance on the status.xml see: http://marc.theaimsgroup.com/?l=xml-cocoon-devm=107883804715745w=2 - View this comment: http://issues.cocoondev.org//browse/FOR-487?page=comments#action_12324 - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Unassigned Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Mon, 2 May 2005 5:43 PM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-489) initial run of forrest from dist fails
The following comment has been added to this issue: Author: David Jung Created: Fri, 29 Apr 2005 12:21 PM Body: I solved the problem thus: Typed: yum install ant which updated by ant from jpackage.org to version 1.6.2-3jpp - which unlike the version I had installed, includes an ant-launcher.jar file. However, the forrest docs say that it includes its own ant version, so it shouldn't depend on having ant installed already. - View this comment: http://issues.cocoondev.org//browse/FOR-489?page=comments#action_12289 - View the issue: http://issues.cocoondev.org//browse/FOR-489 Here is an overview of the issue: - Key: FOR-489 Summary: initial run of forrest from dist fails Type: Bug Status: Unassigned Priority: Critical Project: Forrest Components: Launch 'forrest' Versions: 0.6 Assignee: Reporter: David Jung Created: Fri, 29 Apr 2005 11:32 AM Updated: Fri, 29 Apr 2005 12:21 PM Environment: Redhat Fedora Core 3, Sun JDK 1.5.0-b64 Description: Initial run of forrest per install instructions failed (first time user). Downloaded and untarred 0.6 dist. set env var FORREST_HOME in bash added FORREST_HOME/bin to path. cd'd into top-level and entered 'forrest' on cmd line Result was this: Apache Forrest. Run 'forrest -projecthelp' to list options /usr/bin/build-classpath: error: could not find ant-launcher Java extension for this JVM /usr/bin/build-classpath: error: All specified jars were not found I downloaded and tried an Apr28 snapshot with similar results. (it complained it needed to be built first. Running the build script gave the same error as above) - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Closed: (FOR-486) Enable plugins to supply their own packaged DTDs
Message: The following issue has been closed. Resolver: David Crossley Date: Thu, 28 Apr 2005 7:56 AM This ability is added now. All that plugins need to do, is to add a resources/schema/catalog.xcat and DTDs relative to that. - View the issue: http://issues.cocoondev.org//browse/FOR-486 Here is an overview of the issue: - Key: FOR-486 Summary: Enable plugins to supply their own packaged DTDs Type: Improvement Status: Closed Priority: Major Resolution: FIXED Project: Forrest Components: XML grammars validation Plugins (general issues) Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: Ross Gardler Created: Thu, 21 Apr 2005 3:48 PM Updated: Thu, 28 Apr 2005 7:56 AM Description: Plugins that use their own DTD files (such as simplified docbook and projectInfo) need to have those DTD files extracted to the plugin. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Commented: (FOR-487) generate announcement text from the status.xml
The following comment has been added to this issue: Author: David Crossley Created: Wed, 27 Apr 2005 11:25 PM Body: Moving Ross' suggestion over from task FOR-454 ... I would like to make a suggestion for this issue which will save us time on future releases. If we add an attribute to the action element in skinconfig called announce with a value of true or false (default to false) we can auto generate the announcement of new features.. Furthermore, if we add an element upgrade which contains a textual description of how to upgrade from the previous version we can generate the upgrade document too. These documents, being auto generated would build during the developmentof the project making it easier for someone to return to the project after a while away. I would therefore suggest that in fixing this issue for the 0.7 release we focus on adding this information to status.xml and writing the necessary stylesheets. Remember we only need to produce XDoc as Forrest will give us a neat text version of the document. - View this comment: http://issues.cocoondev.org//browse/FOR-487?page=comments#action_12278 - View the issue: http://issues.cocoondev.org//browse/FOR-487 Here is an overview of the issue: - Key: FOR-487 Summary: generate announcement text from the status.xml Type: New Feature Status: Unassigned Priority: Minor Project: Forrest Components: Plugins (general issues) Fix Fors: 0.8 Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Wed, 27 Apr 2005 11:23 PM Updated: Wed, 27 Apr 2005 11:25 PM Description: By adding some attributes to the actions in status.xml we would be able to use certain entries for the announcement text. - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-454) add content about major changes for this release
The following issue has been updated: Updater: David Crossley (mailto:[EMAIL PROTECTED]) Date: Wed, 27 Apr 2005 11:28 PM Changes: Comment was deleted. - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-454?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-454 Here is an overview of the issue: - Key: FOR-454 Summary: add content about major changes for this release Type: Task Status: Unassigned Priority: Blocker Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 1 Mar 2005 5:15 PM Updated: Wed, 27 Apr 2005 11:28 PM Description: We need notes about the major changes for this release: upgrading_07.xml announcement-0.7.txt RELEASE-NOTES-0.7.txt - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
[JIRA] Updated: (FOR-454) add content about major changes for this release
The following issue has been updated: Updater: David Crossley (mailto:[EMAIL PROTECTED]) Date: Wed, 27 Apr 2005 11:37 PM Comment: There are some notes now added, so reducing issue priority. Changes: priority changed from Blocker to Major - For a full history of the issue, see: http://issues.cocoondev.org//browse/FOR-454?page=history - View the issue: http://issues.cocoondev.org//browse/FOR-454 Here is an overview of the issue: - Key: FOR-454 Summary: add content about major changes for this release Type: Task Status: Unassigned Priority: Major Project: Forrest Components: Documentation and website Fix Fors: 0.7-dev Versions: 0.7-dev Assignee: Reporter: David Crossley Created: Tue, 1 Mar 2005 5:15 PM Updated: Wed, 27 Apr 2005 11:37 PM Description: We need notes about the major changes for this release: upgrading_07.xml announcement-0.7.txt RELEASE-NOTES-0.7.txt - JIRA INFORMATION: This message is automatically generated by JIRA. If you think it was sent incorrectly contact one of the administrators: http://issues.cocoondev.org//secure/Administrators.jspa If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
