Re: How do I move maven.log?
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
project tree. I tend to run it from within vi, and I tell vi to cd to
the package's source directory to make it easier to switch between
multiple files. That means I get maven.log in every directory where I
happen to do a build.
Having it go to ~/.maven or ${basedir} or /tmp or whatever would be much
more useful.
Frankly, it would be even *more* useful if maven didn't produce a log
file unless it had something useful to say. Generating two lines of
output every time - the same two lines that come at the end of the
normal console output - is dumb.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How do I move maven.log?
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 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 project tree. I tend to run it from within
vi, and I tell vi to cd to the package's source directory to
make it easier to switch between multiple files. That means I
get maven.log in every directory where I happen to do a build.
Having it go to ~/.maven or ${basedir} or /tmp or whatever
would be much more useful.
Frankly, it would be even *more* useful if maven didn't
produce a log file unless it had something useful to say.
Generating two lines of output every time - the same two
lines that come at the end of the normal console output - is dumb.
I agree that it should only be generated when there's something useful. I'd personally
prefer to see the log file get
output in the maven.build.dir folder, so it gets cleaned up when I do a maven clean
(and of course a maven clean
shouldn't output a log unless it fails for some reason).
-- Sean T.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I move maven.log?
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 when things are running
fine?
I don't think so. In the past, I've solved this in two ways:
1. Write a custom 'clean' [pre|post]goal (either in maven.xml or a
shared plugin) something like this:
goal name=realclean
attainGoal name=clean/
delete quiet=true
fileset dir=${basedir} includes=**/*~,**/*.log defaultexcludes=no/
/delete
/goal
2. Modify the log4j.properties file inside ${MAVEN_HOME}/lib/maven.jar
The latter option would enable you to fully-qualify the path of the
log file to put it somewhere else.
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I move maven.log?
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 go wrong (or if I ask for a higher-than-normal level of
verbosity).
On Sat, 2003-11-08 at 09:41, Jim Crossley wrote:
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 when things are running
fine?
I don't think so. In the past, I've solved this in two ways:
1. Write a custom 'clean' [pre|post]goal (either in maven.xml or a
shared plugin) something like this:
goal name=realclean
attainGoal name=clean/
delete quiet=true
fileset dir=${basedir} includes=**/*~,**/*.log defaultexcludes=no/
/delete
/goal
2. Modify the log4j.properties file inside ${MAVEN_HOME}/lib/maven.jar
The latter option would enable you to fully-qualify the path of the
log file to put it somewhere else.
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I move maven.log?
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 09/11/2003 03:22:06 PM:
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 go wrong (or if I ask for a higher-than-normal level of
verbosity).
On Sat, 2003-11-08 at 09:41, Jim Crossley wrote:
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 when things are running
fine?
I don't think so. In the past, I've solved this in two ways:
1. Write a custom 'clean' [pre|post]goal (either in maven.xml or a
shared plugin) something like this:
goal name=realclean
attainGoal name=clean/
delete quiet=true
fileset dir=${basedir} includes=**/*~,**/*.log
defaultexcludes=no/
/delete
/goal
2. Modify the log4j.properties file inside ${MAVEN_HOME}/lib/maven.jar
The latter option would enable you to fully-qualify the path of the
log file to put it somewhere else.
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How do I move maven.log?
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? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
