forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] New comment: (FOR-129) Give forrestbot the ability to upload the breadcrumbs.js file
Date Thu, 01 Jan 1970 00:00:00 GMT
The following comment has been added to this issue:

     Author: David Crossley
    Created: Mon, 12 Apr 2004 6:42 AM
       Body:
Thanks for describing this problem - it has bitten many of us from time-to-time. See my followup
discussion in [1] - i think that the version forrest-0.5 on cocoondev.org might be out-of-date
because that version works for me here, and this "un-expanded tokens" issue was fixed.

So do you really need the ability to upload an alternate specific breadcrumbs.js or it just
that the default one is broken?

---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-129


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-129
    Summary: Give forrestbot the ability to upload the breadcrumbs.js file
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: Forrestbot
   Versions:
             0.7

   Assignee: 
   Reporter: Glen Mazza

    Created: Mon, 12 Apr 2004 1:02 AM
    Updated: Mon, 12 Apr 2004 1:02 AM
Environment: standard Apache forrestbot at forrestbot.cocoondev.org

Description:
(From the XML Apache FOP team)

As discussed here [1], after running the publish command from the forrestbot we need to manually
update the breadcrumbs.js within xml-site/targets/fop/skin directory [2].  (The forrestbot
overwrites our breadcrumbs.js with a version that does not work.)

I see no way to currently switch the buggy version that the Forrestbot uses to overwrite the
breadcrumbs.js file.

As an enhancement, to save us the need for the manual reversion everytime we publish the site,
give Forrestbot the ability to read content/skin/breadcrumbs.js in our project directory [3]),
and use *that* file when it publishes to xml-site.

Of course, content/xdocs/* and content/skins/** already transfer over (as defined here [4],
also see [5][6] for the Forrest site, for example.)  We just need the ability for content/skin/breadcrumbs.js
to do the same.

Thanks,
Glen Mazza
Apache FOP Team 

[1] http://marc.theaimsgroup.com/?l=forrest-dev&m=108147561332545&w=2
[2] http://cvs.apache.org/viewcvs.cgi/xml-site/targets/fop/skin/breadcrumbs.js
[3] http://cvs.apache.org/viewcvs.cgi/xml-fop/src/documentation/content/
[4] http://xml.apache.org/forrest/forrest-contract.html#TheProject+Can%3A
[5] http://cvs.apache.org/viewcvs.cgi/xml-forrest/src/documentation/content/skins/skins.xml
[6] http://cvs.apache.org/viewcvs.cgi/xml-site/targets/forrest/skins/



---------------------------------------------------------------------
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


Mime
View raw message