[
http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MDEPLOY-44:
-------------------------------------
Attachment: MDEPLOY-44.zip
The approach described by Kalle is not a workaround but the primary means to
control the snapshot naming. The attached demo project works for me.
The only pitfall I could imagine here is that people have a dedicated
{{<snapshotRepository>}} configured in their POM but set the
{{<uniqueVersion>}} flag on the {{<repository>}} element instead of
{{<snapshotRepository>}}.
bq. But, it'd be very useful if you could override uniqueVersion setting from
the command line.
That's already possible via a profile that overrides {{<snapshotRepository>}}.
Please provide more details (debug log, demo project) if the usage of
{{<uniqueVersion>false</uniqueVersion>}} really does not work.
> 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
> 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 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
