On Sun, 2003-11-09 at 01:40, [EMAIL PROTECTED] wrote:
placing the log in ~/.maven makes sense, except when you run multiple
mavens simultaneously.
Placing it in the current working directory doesn't make any more sense.
The --find option lets you run maven from pretty much anywhere in your
Your opinion on the utility to allow users the option to filter on events captured in
a log is noted.
-Original Message-
From: Sean Timm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 10, 2003 11:24 PM
To: Maven Users List
Subject: RE: How do I move maven.log?
On Sun, 2003-11-09
Hi Scott
Scott Brickner [EMAIL PROTECTED] writes:
Maven is littering my project folders with maven.log files, none of
which say anything useful (just info on the running time). Is there
some officially supported way for me to make it put that log
somewhere else? Or to suppress it entirely
Does this seem stupid to anyone else? I mean, the log files are there to
analyze maven when things go wrong, they aren't specific to the project
- so why should they end up in the project directory? ~/.maven would
make more sense, I'd think. And they shouldn't have *anything* unless
something does
Scott,
placing the log in ~/.maven makes sense, except when you run multiple
mavens simultaneously.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc
Scott Brickner [EMAIL PROTECTED] wrote on
Maven is littering my project folders with maven.log files, none of
which say anything useful (just info on the running time). Is there some
officially supported way for me to make it put that log somewhere else?
Or to suppress it entirely when things are running fine?
