[ http://jira.codehaus.org/browse/MINSTALL-13?page=all ]
Brett Porter closed MINSTALL-13:
--------------------------------
Assign To: Brett Porter
Resolution: Won't Fix
you mean the same as "mvn clean" ? You would be better to bind this to the
install phase in a profile:
{code:xml}
<profile>
<id>cleaning-profile</id>
<plugins>
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<executions>
<execution>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</profile>
{code}
and run
{noformat}
mvn -P clean-profile install
{noformat}
> After successful installation of artifact to the repository, do optional
> clean up.
> ----------------------------------------------------------------------------------
>
> Key: MINSTALL-13
> URL: http://jira.codehaus.org/browse/MINSTALL-13
> Project: Maven 2.x Install Plugin
> Type: New Feature
> Reporter: Napoleon Esmundo C. Ramirez
> Assignee: Brett Porter
>
>
> 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 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
