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]
