You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@forrest.apache.org by Addi <ad...@rocktreesky.com> on 2005/07/05 17:56:26 UTC
capturing error output
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
Re: capturing error output
Posted by Thorsten Scherler <th...@apache.org>.
On Tue, 2005-07-05 at 12:57 -0400, Addi wrote:
> Thanks Thorsten! That did the trick.
>
> - Addi
>
> Thorsten Scherler wrote:
>
> >shoot in the dark:
> >forrest run 2&>log.txt
> >
> >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
> >>
> >>
> >>
>
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: forrestbot docs (Was: capturing error output)
Posted by Ross Gardler <rg...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
>
>>Addi wrote:
>>
>>>Thanks for pointing me there Diwaker. I banged my head for a while
>>>because I was a bit confused, but then I stumbled upon the correct,
>>>magically aligned buildfile and it worked like a charm. I may have some
>>>mods to the documentation on that, for dummies like me. I will have to
>>>play with this some more tomorrow.
>>
>>Hey, I've been a dev on Forrest for years and I've been avoiding
>>learning Forrestbot in te hope someone improves the docs. I'll apply
>>your patches personally ;-)
>
>
> Really, i had no trouble following the current docs and i had
> no experience with forrestbot when i started. Anyway, it will
> be interesting to see what changes are needed.
Maybe I tried too late at night then ;-)
Ross
forrestbot docs (Was: capturing error output)
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Addi wrote:
> >Thanks for pointing me there Diwaker. I banged my head for a while
> >because I was a bit confused, but then I stumbled upon the correct,
> >magically aligned buildfile and it worked like a charm. I may have some
> >mods to the documentation on that, for dummies like me. I will have to
> >play with this some more tomorrow.
>
> Hey, I've been a dev on Forrest for years and I've been avoiding
> learning Forrestbot in te hope someone improves the docs. I'll apply
> your patches personally ;-)
Really, i had no trouble following the current docs and i had
no experience with forrestbot when i started. Anyway, it will
be interesting to see what changes are needed.
-David
Re: capturing error output
Posted by Ross Gardler <rg...@apache.org>.
Addi wrote:
> Thanks for pointing me there Diwaker. I banged my head for a while
> because I was a bit confused, but then I stumbled upon the correct,
> magically aligned buildfile and it worked like a charm. I may have some
> mods to the documentation on that, for dummies like me. I will have to
> play with this some more tomorrow.
Hey, I've been a dev on Forrest for years and I've been avoiding
learning Forrestbot in te hope someone improves the docs. I'll apply
your patches personally ;-)
Ross
Re: capturing error output
Posted by David Crossley <cr...@apache.org>.
Kevin wrote:
> Addi wrote:
> >Diwaker Gupta wrote:
> >
> >>>Apparently Forrest doesn't like the 2&> "target". Output using the
> >>>regular > comes back successful. Any ideas how to get around that? I
>
> cmd >logfile 2>&1
>
> Redirects stderr to were stdout redirect was previously defined in
> command line.
Thanks very much for seeting that straight Kevin.
Addi that is nothing to do with Forrest. That is a
UNIX command to redirect output.
-David
Re: capturing error output
Posted by Kevin <ke...@mail.portland.co.uk>.
Addi wrote:
> Diwaker Gupta wrote:
>
>>> Apparently Forrest doesn't like the 2&> "target". Output using the
>>> regular > comes back successful. Any ideas how to get around that? I
cmd >logfile 2>&1
Redirects stderr to were stdout redirect was previously defined in
command line.
Kevin.
>>> 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.
>>>
>>
>>
>> You might want to consider using Forrestbot
>> (http://forrest.apache.org/tools/forrestbot.html) -- its flexible and
>> powerful, can work over SSH, FTP; use CVS/SVN and send you emails with
>> build results
>> (http://forrest.apache.org/tools/forrestbot.html#notify.email)
>>
>>
>>
> Thanks for pointing me there Diwaker. I banged my head for a while
> because I was a bit confused, but then I stumbled upon the correct,
> magically aligned buildfile and it worked like a charm. I may have some
> mods to the documentation on that, for dummies like me. I will have to
> play with this some more tomorrow.
>
> - Addi
>
>
>
Re: capturing error output
Posted by Addi <ad...@rocktreesky.com>.
Diwaker Gupta wrote:
>>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.
>>
>>
>
>You might want to consider using Forrestbot
>(http://forrest.apache.org/tools/forrestbot.html) -- its flexible and
>powerful, can work over SSH, FTP; use CVS/SVN and send you emails with
>build results (http://forrest.apache.org/tools/forrestbot.html#notify.email)
>
>
>
Thanks for pointing me there Diwaker. I banged my head for a while
because I was a bit confused, but then I stumbled upon the correct,
magically aligned buildfile and it worked like a charm. I may have some
mods to the documentation on that, for dummies like me. I will have to
play with this some more tomorrow.
- Addi
Re: capturing error output
Posted by Diwaker Gupta <di...@gmail.com>.
> 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.
You might want to consider using Forrestbot
(http://forrest.apache.org/tools/forrestbot.html) -- its flexible and
powerful, can work over SSH, FTP; use CVS/SVN and send you emails with
build results (http://forrest.apache.org/tools/forrestbot.html#notify.email)
--
Diwaker Gupta
http://resolute.ucsd.edu/diwaker
Re: capturing error output
Posted by Addi <ad...@rocktreesky.com>.
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
>>>>
>>>>
>>>>
>>>>
>>>>
>>
>>
Re: capturing error output
Posted by Thorsten Scherler <th...@apache.org>.
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
> >
> >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
> >>
> >>
> >>
>
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
Re: capturing error output
Posted by Addi <ad...@rocktreesky.com>.
Thanks Thorsten! That did the trick.
- Addi
Thorsten Scherler wrote:
>shoot in the dark:
>forrest run 2&>log.txt
>
>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
>>
>>
>>
Re: capturing error output
Posted by Thorsten Scherler <th...@apache.org>.
shoot in the dark:
forrest run 2&>log.txt
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
>
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)