[jira] Closed: (MPXDOC-124) clean doesn't clean velocity.log.1

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: David Eric Pugh
       Date: Tue, 26 Oct 2004 5:05 AM

Fixed with a postgoal on clean:clean.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-124

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPXDOC-124
    Summary: clean doesn't clean velocity.log.1
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-xdoc-plugin
   Fix Fors:
             1.9

   Assignee: David Eric Pugh
   Reporter: Shinobu Kawai

    Created: Mon, 25 Oct 2004 1:20 AM
    Updated: Tue, 26 Oct 2004 5:05 AM
Environment: Any time Velocity spits over 100KB of log

Description:
Currently, clean:clean only cleans velocity.log, and not velocity.log.1.

By default, Velocity uses the RollingFileAppender with maxBackupIndex=1 and maximumFileSize=100000.  Which means, if the log file exceeds 100000 bytes, the log file will be rolled to velocity.log.1 and a new log file will start.  If the clean plugin is going to clean the original log, it should also clean the rolled log.

(Or, I guess it could be put in the xdoc plugin.)


---------------------------------------------------------------------
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org