[
http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114948
]
Kalle Korhonen commented on MDEPLOY-44:
---------------------------------------
As a workaround, you can set uniqueVersion to false in distributionManagement
section of your pom, e.g:
<distributionManagement>
<repository>
<id>my-repo</id>
<name>My Internal Repository</name>
<url>scp://my-repo.com/repo</url>
<uniqueVersion>false</uniqueVersion>
</repository>
</distributionManagement>
But, it'd be very useful if you could override uniqueVersion setting from the
command line.
> Add uniqueVersion parameter to deploy goal as deploy-file goal
> --------------------------------------------------------------
>
> Key: MDEPLOY-44
> URL: http://jira.codehaus.org/browse/MDEPLOY-44
> Project: Maven 2.x Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 2.2.1
> Environment: Maven 2.0.4
> Reporter: David Vicente
>
> We developp a big application which we deploy in our local repository with
> deploy goal.
> But deploy goal use a timestamp to name the archive file and we have many
> problems of disk space that obliges us to clean manually our local repository.
> it's possible to add the uniqueVersion parameter to deploy goal as done with
> deploy-file goal which would remove us the obligation to purge ?
> thanks
--
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
