[
https://issues.apache.org/jira/browse/MINSTALL-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965849#comment-17965849
]
Olivier Lamy commented on MINSTALL-13:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-install-plugin#262|https://github.com/apache/maven-install-plugin/issues/262].
> After successful installation of artifact to the repository, do optional
> clean up.
> ----------------------------------------------------------------------------------
>
> Key: MINSTALL-13
> URL: https://issues.apache.org/jira/browse/MINSTALL-13
> Project: Maven Install Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Reporter: Nap Ramirez
> Assignee: Brett Porter
> Priority: Major
>
> After successful installation of artifact to the repository, do optional
> clean up.
> This is to conservatively utilize hard disk space when building very large
> projects with many modules.
> In a project I'm building, composed of ~50 modules, I usually run out of hard
> disk space. Currently, Maven cleans up first (frees hd space), then
> generates sources (consumes hd space), then generates output files(consumes
> more hd space), then installing(consumes even more hd space), all in batch
> mode, imagine the space that would be consumed! To avoid using up too much
> hd space, I suggest that for every installation (every module), a clean is
> optional.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
