The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 4 Aug 2003 9:42 AM
Changes:
timeoriginalestimate changed from 0
timeestimate changed from 0 minutes
Fix Version changed to 1.1
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-385&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-385
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-385
Summary: logs should go to dir maven finds with --find
Type: Improvement
Status: Unassigned
Priority: Minor
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.1
Versions:
1.0-beta-9
Assignee:
Reporter: Brian Leonard
Created: Fri, 11 Apr 2003 2:07 AM
Updated: Mon, 4 Aug 2003 9:42 AM
Description:
If using the --find option, the logs should go to the directory in which maven finds
the pom. Currently they are put in the dir from which the maven command is run, which
tends to leave log files all throughout the source tree.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
