The following issue has been updated:

    Updater: Shinobu Kawai (mailto:[EMAIL PROTECTED])
       Date: Mon, 25 Oct 2004 9:33 PM
    Comment:
Okay, here's the patch to move the Velocity log cleaning to the xdoc plugin.  As for 
the maven.clean.include extension, I think a new issue should be filed.
    Changes:
             Attachment changed to xdoc-clean.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPCLEAN-4?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPCLEAN-4

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

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-clean-plugin

   Assignee: David Eric Pugh
   Reporter: Shinobu Kawai

    Created: Mon, 25 Oct 2004 1:20 AM
    Updated: Mon, 25 Oct 2004 9:33 PM
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to