forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-204) Broken link summary include the referencing URLs
Date Tue, 12 Oct 2004 02:26:38 GMT
The following comment has been added to this issue:

     Author: David Crossley
    Created: Mon, 11 Oct 2004 9:26 PM
       Body:
(Bringing over Rick's comment from the duplicate issue FOR-323.)

In particular, it would aid in identifying problems as found in FOR-321.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-204?page=comments#action_11646

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-204

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-204
    Summary: Broken link summary include the referencing URLs
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Core operations
   Fix Fors:
             0.7
   Versions:
             HEAD

   Assignee: 
   Reporter: Lorenz Froihofer

    Created: Sat, 26 Jun 2004 11:15 AM
    Updated: Mon, 11 Oct 2004 9:26 PM

Description:
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)">
  <name>linkdeddoc.html</name>
  <document>/file-path/test1.xml</document>
  <document>/file-path/test2.xml</document>
  <document>/file-path/test3.xml</document>
</link>


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


Mime
View raw message