forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian M Dube (JIRA)" <>
Subject [jira] Closed: (FOR-752) Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory
Date Wed, 12 Jan 2011 06:43:47 GMT


Brian M Dube closed FOR-752.

       Resolution: Fixed
    Fix Version/s:     (was: 0.10)

Contributed patch applied with thanks.

> Forrestbot "build" workstage creates spurious "build/webapp/WEB-INF/logs" directory
> -----------------------------------------------------------------------------------
>                 Key: FOR-752
>                 URL:
>             Project: Forrest
>          Issue Type: Bug
>          Components: Tool: Forrestbot
>    Affects Versions: 0.7, 0.8, 0.9-dev
>            Reporter: Richard Calmbach
>            Priority: Minor
>             Fix For: 0.9-dev
> When running Forrestbot with the default value for property "" (namely
"work/${}"), "" is set to the same value and consequently,
"project.webapp" is set to "work/${}/webapp". However, one of the two "logs"
directories continues to be created at "build/webapp/WEB-INF/logs", suggesting that somewhere
a hardcoded value is used instead of ${project.webapp}. The mkdir command for this "logs"
directory is not in any of the Ant build files in the Forrest distribution; it must be in
one of the Java classes, probably in a class related to logging. I forced an I/O failure by
turning off all permissions on build/webapp and running "forrest -f build.xml build". This
yielded a stacktrace that originated 7 calls before:
> org.apache.avalon.excalibur.logger.factory.FileTargetFactory.createTarget(
> The remaining 7 invokations were not displayed (just "... 7 more").
> The upshot of this bug is that running "forrest -f build.xml clean" misses the "logs"
directory in the unexpected location. My workaround right now is to use a custom "clean-all"
target that depends on "clean" and that deletes the spurious "build/webapp" directory.

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

View raw message