Thorsten Scherler wrote:
On Tue, 2005-07-05 at 12:57 -0400, Addi wrote:
Thanks Thorsten! That did the trick.
:)
Thanks for reporting back.
thorsten
- Addi
Thorsten Scherler wrote:
shoot in the dark:
forrest run 2&>log.txt
Hm, darnit, I did some more testing and it does give me the full error
output to file but it now always reports the build as failed with this
error:
BUILD FAILED
Target `2' does not exist in this project.
Apparently Forrest doesn't like the 2&> "target". Output using the
regular > comes back successful. Any ideas how to get around that? I
am writing a cron to build forrest each night and email me the error
output if the build fails so I can check into it. Since the 2&> makes
every build fail, it emails me everytime, even if the build really was
successful. I was hoping it maybe gave a unique exit code but it gives
the same as a broken link, so I can't use that to filter this particular
error out.
Thanks for the help.
Addi
HTH
On Tue, 2005-07-05 at 11:56 -0400, Addi wrote:
Hello all,
I am using 0.7 on linux and am trying to get validation error output to
go to a file for later review. I have done forrest site > for.log, but
that only gives me the output *up to* the error message. Specifically
it gives me all output up to and including the line "validate-xdocs:"
but doesn't give me the important bit after that tells me why it didn't
validate. My build/webapp/WEB-INF/ logs are empty.
Does forrest log the validation errors somewhere? If not, how can I
capture them?
Thanks for any pointers.
Addi
