[
http://jira.codehaus.org/browse/MCLEAN-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MCLEAN-32.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Assignee: Benjamin Bentmann
Fixed in [r897682|http://svn.apache.org/viewvc?view=revision&revision=897682].
On a test structure that resembles a binary tree of depth 14 with two files at
each level besides the two child directories, I observed the following
improvements:
{noformat}
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ test ---
[INFO] Deleting file set: M:\test\. (included: [], excluded: [pom.xml])
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3:50.797s
[INFO] Finished at: Sun Jan 10 18:34:49 CET 2010
[INFO] Final Memory: 1M/42M
[INFO] ------------------------------------------------------------------------
{noformat}
{noformat}
[INFO] --- maven-clean-plugin:2.4-SNAPSHOT:clean (default-clean) @ test ---
[INFO] Deleting M:\test (includes = [], excludes = [pom.xml])
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 41.938s
[INFO] Finished at: Sun Jan 10 18:39:39 CET 2010
[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------
{noformat}
i.e. the memory used dropped from 42 MB to 4MB.
> Out of Memory Error cleaning target directory with *large* number of
> sub-directories
> ------------------------------------------------------------------------------------
>
> Key: MCLEAN-32
> URL: http://jira.codehaus.org/browse/MCLEAN-32
> Project: Maven 2.x Clean Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: maven-2.0.8, solaris, jdk 1.6.0_05
> Reporter: Ryan Sonnek
> Assignee: Benjamin Bentmann
> Priority: Critical
> Fix For: 2.4
>
> Attachments: output.txt
>
>
> running mvn clean on a target directory with a *large* number of sub
> directories causes an OutOfMemoryError. The plexus DirectoryScanner seems to
> be the major culprit from the stacktrace.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
