[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
Re: 0.7 is nearly there
Ross Gardler wrote: Juan Jose Pablos wrote: Ross Gardler wrote: There are now only 5 issues open on the 0.7 release. 3 of them are documentation issues, so anyone can pitch in here. 2 of them are Cocoon issues and will either be fixed with a cocoon upgrade, or we will not be able to fix them for 0.7 Is it time we planned for a release date? (again) The Lazy mode: true output looks very awfull Yes, that will go with a cocoon upgrade that needs to be done for two of the outstanding issues anyway. Which issues are you talking about Ross? Are they critical? I reckon that we should not wait for a Cocoon upgrade. I will attend to FOR-500 verifying the licenses for supporting products and generally ensure that our own work is properly licensed, but i don't want to do that until just before release in case more stuff gets added. As we have said before, we do not need to solve every issue that is listed. --David
Re: 0.7 is nearly there
David Crossley wrote: Ross Gardler wrote: Juan Jose Pablos wrote: Ross Gardler wrote: There are now only 5 issues open on the 0.7 release. 3 of them are documentation issues, so anyone can pitch in here. 2 of them are Cocoon issues and will either be fixed with a cocoon upgrade, or we will not be able to fix them for 0.7 Is it time we planned for a release date? (again) The Lazy mode: true output looks very awfull Yes, that will go with a cocoon upgrade that needs to be done for two of the outstanding issues anyway. Which issues are you talking about Ross? Are they critical? Lazy Mode: True messages are just an output issue, I'm good with that. character entities (e.g. ampersand) are expanded again for href or src attributes (http://issues.cocoondev.org/browse/FOR-241 ) is marked as major, comments indicate it is fixed in Cocoon trunk. This issue only affects users running in dynamic mode since the encoding of request parameters when creating a static site breaks the links anyway (there can be no '?' in a filename, so no static link can be made) The other issue seems to have been closed (or moved). I reckon that we should not wait for a Cocoon upgrade. Since I don't have Linux right now and Juan (I think it was Juan who took the time to try the upgrade, apologies if I'm not giving the credit to the right person) has encountered problems with the upgrade I am +1 on going ahead without the upgrade. Lets just say if we don't get a -1 in the next three days we will go ahead and move those issues to 0.8. If someone wants to -1 this proposal then *they* will have to do the upgrade - fair enough? I will attend to FOR-500 verifying the licenses for supporting products and generally ensure that our own work is properly licensed, but i don't want to do that until just before release in case more stuff gets added. I'll finish FOR-470 (update seed site) I'll also finsih FOR-454, major changes are now marked up in status.xml, we need a stylesheet for projectInfo to allow them to be included in relevant docs with xi:include (unless someone gets there first of course). That leaves: FOR-391 website docs/site split http://issues.cocoondev.org/browse/FOR-391 Which I believe is complete but for thorough testing, the creation of the 0.8 set of docs and the move to 0.7 as the default (the move should be done as part of the release process) This is currently assigned to David, but I believe this is a job for many eyes now. We need people to look for problems. Shall we post a request to the user list to check these docs? --- FOR-465 Logging Error: Writing event to closed stream. http://issues.cocoondev.org/browse/FOR-465 I have no idea what is causing this so someone needs to do some initial evaluation. I'd be OK with this still being in the release as it does not affect the usability of Forrest. So again, I propose we release without this fixed unless someone votes -1 *and* fixes it for us. --- Of course, my proposal to require a -1 and a fix could be seen as railroading the release, it is a step ahead of lazy consensus, so I won't argue the point if devs feel this is not an appropriate. I just want to get this release out. Ross
[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
Re: 0.7 is nearly there
Ross Gardler wrote: David Crossley wrote: Ross Gardler wrote: Yes, that will go with a cocoon upgrade that needs to be done for two of the outstanding issues anyway. Which issues are you talking about Ross? Are they critical? Lazy Mode: True messages are just an output issue, I'm good with that. character entities (e.g. ampersand) are expanded again for href or src attributes (http://issues.cocoondev.org/browse/FOR-241 ) is marked as major, comments indicate it is fixed in Cocoon trunk. Ah, no, i see that my comment has misled you. I just meant that the Cocoon Hello World sample did not exhibit the problem. It might be our sitemaps. Anyway, it is a known problem, we don't actually need to fix it. This issue only affects users running in dynamic mode since the encoding of request parameters when creating a static site breaks the links anyway (there can be no '?' in a filename, so no static link can be made) The other issue seems to have been closed (or moved). I reckon that we should not wait for a Cocoon upgrade. Since I don't have Linux right now and Juan (I think it was Juan who took the time to try the upgrade, apologies if I'm not giving the credit to the right person) has encountered problems with the upgrade I am +1 on going ahead without the upgrade. Lets just say if we don't get a -1 in the next three days we will go ahead and move those issues to 0.8. If someone wants to -1 this proposal then *they* will have to do the upgrade - fair enough? Yes Juan==Cheche did try, and he contacted cocoon-dev and got positive reply to his specific issue. However other people are saying cocoon trunk is not stable. I will attend to FOR-500 verifying the licenses for supporting products and generally ensure that our own work is properly licensed, but i don't want to do that until just before release in case more stuff gets added. I'll finish FOR-470 (update seed site) I'll also finsih FOR-454, major changes are now marked up in status.xml, we need a stylesheet for projectInfo to allow them to be included in relevant docs with xi:include (unless someone gets there first of course). FOR-454 was actually about adding more content to upgrading_07 doc. That should be a group effort, but if you get time to try that would be good. The extra improvement about getting announcement automatically notes out of the status.xml is a bonus, we don't need it for release. We can just manually write the etc/announcement-0.7.txt That leaves: FOR-391website docs/site split http://issues.cocoondev.org/browse/FOR-391 Which I believe is complete but for thorough testing, the creation of the 0.8 set of docs and the move to 0.7 as the default (the move should be done as part of the release process) This is currently assigned to David, but I believe this is a job for many eyes now. We need people to look for problems. Shall we post a request to the user list to check these docs? Job is done. That is a good idea. The dev list too. There must be a lot of lurkers. What would we ask? We don't want reports that we need more docs about so-and-so or that we need to create a beginners tutorial. Mainly we need to find instructions and pathnames that still relate to 0.6 version. Anything else can wait until 0.8-dev --- FOR-465Logging Error: Writing event to closed stream. http://issues.cocoondev.org/browse/FOR-465 I have no idea what is causing this so someone needs to do some initial evaluation. I'd be OK with this still being in the release as it does not affect the usability of Forrest. So again, I propose we release without this fixed unless someone votes -1 *and* fixes it for us. --- Of course, my proposal to require a -1 and a fix could be seen as railroading the release, it is a step ahead of lazy consensus, ... What about when that person gets drawn off by other itches and we have a half-finished solution. Delay. ... so I won't argue the point if devs feel this is not an appropriate. I just want to get this release out. Don't we all. --David
[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
Release notes generation
I just committed changes to the projectinfo plugin that will generate release notes for a particular version of forrest from status.xml. If you request http://localhost:/releaseNotes_0.7-dev.html you will be given the release notes for 0.7. I also enabled the Text plugin to allow http://localhost:/releaseNotes_0.7-dev.txt However, there are a few problems to be resolved with the layout of this version. The notes are created from status.xml. Actions that have @importance=high will appear in the release notes. The initial text in the page comes from the new (optional) element notes. In future we should write our status.xml actions with this in mind: - should it be importance=high? - will the action read correctly in the release notes? Let me know if you can see any improvements to be made. Ross
[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
