> 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]
