You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/07/17 04:15:40 UTC
[issues] New comment: (FOR-202) Custom sitemap.xmap causes hang
The following comment has been added to this issue:
Author: Dave Brondsema
Created: Sat, 17 Jul 2004 4:15 AM
Body:
The following pipeline needs to be removed manually from the project sitemap.xmap. Or find some way to not select this when it is in the project sitemap already. I have no idea how do to this, though. Is there some way we can get the current filename and see if it is the same as {project:sitemap}?
<map:pipeline internal-only="false">
<map:select type="exists">
<map:when test="{project:sitemap}">
<map:mount uri-prefix="" src="{project:sitemap}" check-reload="yes" />
</map:when>
</map:select>
</map:pipeline>
---------------------------------------------------------------------
View the issue:
http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-202
Here is an overview of the issue:
---------------------------------------------------------------------
Key: FOR-202
Summary: Custom sitemap.xmap causes hang
Type: Bug
Status: Unassigned
Priority: Major
Project: Forrest
Component: Core operations
Fix For: 0.6
Versions:
HEAD
Assignee:
Reporter: Lorenz Froihofer
Created: Wed, 23 Jun 2004 11:56 PM
Updated: Thu, 24 Jun 2004 1:57 AM
Description:
If there is a sitemap.xmap file in the "project.content-dir", the build process of a site (target: "site") will hang with an OutOfMemoryError.
---------------------------------------------------------------------
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/jira//Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira