forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] Created: (FOR-204) Broken Link Summary
Date Thu, 01 Jan 1970 00:00:00 GMT
Message:

  A new issue has been created in JIRA.

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

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


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

   Assignee: 
   Reporter: Lorenz Froihofer

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

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