[
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: This does not seem to work (still or anymore?), for me with using 3.3.9
and this in a project's pom.xml:
{noformat} <distributionManagement>
<snapshotRepository>
<id>karaf-system</id>
<url>file:///tmp/system/</url>
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>
</distributionManagement>{noformat}
mvn deploy still leads to a
/tmp/system/**/hello-impl-0.1.0-20160618.162823-1.jar :-()
> 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)
