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
