forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [issues] Updated: (FOR-204) Broken Link Summary
Date Thu, 01 Jan 1970 00:00:00 GMT
The following issue has been updated:

    Updater: David Crossley (
       Date: Sat, 26 Jun 2004 11:55 AM
There is some discussion of this in the old email archives. It would be up to the Cocoon CLI
to do this. There are various powers of CLI that we are not using.

[Version] [HEAD] was added
[Fix For] set to [0.7]

For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: FOR-204
    Summary: Broken Link Summary
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
  Component: Core operations
    Fix For: 0.7

   Reporter: Lorenz Froihofer

    Created: Sat, 26 Jun 2004 11:15 AM
    Updated: Sat, 26 Jun 2004 11:55 AM

It would be helpful if the brokenlinks.xml file contained for each broken link a summary of
files where the broken link occured.

Example: test1.xml, test2.xml and test3.xml have a link to linkeddoc.xml. Now the linkeddoc.xml
is moved to another directory but the test?.xml files are not updated. The brokenlinks.xml
should contain something like:

<link message="/old-file-path/linkeddoc.xml (No such file or directory)">

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message