> > Dropping a "maven.log" file everywhere in the current working > > directory isn't too nice, either. Send output to the > console or make > > it writeable to a file with e.g. -f maven.log. > Raise this one as a report in Jira. > > Where would you prefer the output go, most of it's debugging > stuff. The > console doesn't make much sense. The -f option sounds ok, or --log?
Shouldn't this be the same as everything else? If its mostly debugging, it should be logged with a debug priority, I would think. I don't know how possible this is. As for the commons-logging stuff - I was surprised to find it isn't in the latest Javadoc. Maybe we need to hard code a log4j solution and just give an unsupported error if something else is configured, and then try and get it implemented in commons-logging. I believe log4j and jdk 1.4 both support it, so it shouldn't be a big deal. Cheers, Brett
