forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [issues] Updated: (FOR-165) brokenlinks file is generated in forrest.home rather than project.home
Date Thu, 01 Jan 1970 00:00:00 GMT
The following issue has been updated:

    Updater: Nicola Ken Barozzi (mailto:nicolaken@apache.org)
       Date: Fri, 11 Jun 2004 12:45 PM
    Changes:
[Fix For] set to [0.6]

---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-165&page=history

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

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


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-165
    Summary: brokenlinks file is generated in forrest.home rather than project.home
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
  Component: Core operations
    Fix For: 0.6
   Versions:
             HEAD

   Assignee: 
   Reporter: David Crossley

    Created: Sat, 5 Jun 2004 8:30 AM
    Updated: Fri, 11 Jun 2004 12:45 PM

Description:
The Forrest build system specifies that the brokenlinks.xml file will be generated in the
project build directory. We used to call the CLI directly and specify its parameters. However,
now we just tell it where to find the cli.xconf file. This config file has a hard-coded path
for ../brokenlinks.xml so it just gets generated in forrest.home

If you have two or three different projects, then they will clash because they all write to
the same brokenlinks file.

Symptom of a larger issue - how to call the CLI properly and how best to configure it.


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