[ 
https://issues.apache.org/jira/browse/DERBY-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew McIntyre updated DERBY-3293:
-----------------------------------

    Attachment: derby-3292-v1.diff

Attaching patch with necessary changes to files in the src directory, omitted 
changes in the build directory, as all HTML output was affected by the change. 
Main things to note are that a default locationmap was added, and an image was 
moved to get around an odd issue with Cocoon where otherwise Cocoon would 
report the file as missing even though it was clearly present in the 
filesystem. Without any additional information - the Cocoon log message was 
'null' - to go on, I tried moving the file and that fixed the problem. I left 
the file in the old location in the build directory to prevent broken links.

While this upgrade fixes our issue with FOR-555, FOR-480 has been closed as no 
fix intended, with a workaround that doesn't really work for us. I will check 
the changes in and update the website and release instructions shortly.

> Upgrade Derby website build to Forrest 0.8
> ------------------------------------------
>
>                 Key: DERBY-3293
>                 URL: https://issues.apache.org/jira/browse/DERBY-3293
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.4.0.0
>            Reporter: Andrew McIntyre
>            Priority: Minor
>             Fix For: 10.4.0.0
>
>         Attachments: derby-3292-v1.diff
>
>
> Forrest 0.8 was released in April 2007, and contains a fix for FOR-555, which 
> complicates the release process by requiring the release manager to carefully 
> reinsert HTML comments needed by the mirror script for the download pages.  
> The Derby website build should be updated to use Forrest 0.8 to elimiinate 
> this additional step from the release process.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to