You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/10/25 10:52:08 UTC

[jira] Commented: (MPCLEAN-4) clean doesn't clean velocity.log.1

The following comment has been added to this issue:

     Author: David Eric Pugh
    Created: Mon, 25 Oct 2004 4:51 AM
       Body:
While your patch would work for velocity.log.1, it won't work for velocity.log.2 or name your extra artifact.  

If you are interested, look at how other plugins implement includes and excludes patterns.   PMD and JCoverage would be examples.

What you really want are a list of maven.clean.include patterns that you would specify:

maven.clean.include=*.log.*,myOtherLog.log

Eric
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MPCLEAN-4?page=comments#action_25757

---------------------------------------------------------------------
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: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-clean-plugin

   Assignee: 
   Reporter: Shinobu Kawai

    Created: Mon, 25 Oct 2004 1:20 AM
    Updated: Mon, 25 Oct 2004 4:51 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