You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/06/18 17:25:05 UTC
[jira] [Issue Comment Deleted] (MDEPLOY-44) Add uniqueVersion
parameter to deploy goal as deploy-file goal
[ https://issues.apache.org/jira/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Heinz Marbaise updated MDEPLOY-44:
---------------------------------------
Comment: was deleted
(was: As far as as i know: Maven 3.0+ always uses unique snapshots. Can't be turned off. Why not open a new issue with reference to this instead of editing an existing. BTW: Can you give a more detailed description of the use case here?)
> Add uniqueVersion parameter to deploy goal as deploy-file goal
> --------------------------------------------------------------
>
> Key: MDEPLOY-44
> URL: https://issues.apache.org/jira/browse/MDEPLOY-44
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Affects Versions: 2.2.1
> Environment: Maven 2.0.4
> Reporter: David Vicente
> Assignee: Benjamin Bentmann
> Attachments: MDEPLOY-44.zip
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)