You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David vicente (JIRA)" <ji...@codehaus.org> on 2006/12/12 09:37:47 UTC
[jira] Created: (MDEPLOY-44) Add uniqueVersion parameter to deploy
goal as deploy-file goal
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
[jira] Updated: (MDEPLOY-44) Add uniqueVersion parameter to deploy
goal as deploy-file goal
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MDEPLOY-44:
--------------------------------
Reporter: David Vicente (was: David vicente)
> 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
[jira] Commented: (MDEPLOY-44) Add uniqueVersion parameter to
deploy goal as deploy-file goal
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162331#action_162331 ]
Benjamin Bentmann commented on MDEPLOY-44:
------------------------------------------
There was indeed a bug with the handling of {{<uniqueVersion>}} in the Maven core (MNG-3885) in combination with profiles and inheritance.
> 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
> 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 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
[jira] Commented: (MDEPLOY-44) Add uniqueVersion parameter to
deploy goal as deploy-file goal
Posted by "Thorsten Möller (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162310#action_162310 ]
Thorsten Möller commented on MDEPLOY-44:
----------------------------------------
The proposed workaround by Kalle Korhonen does not work for me either (using Maven 2.0.9 and deploy plugin 2.4).
I really appreciate if this issue would be fixed!
Thanks,
Thorsten
> 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
[jira] Closed: (MDEPLOY-44) Add uniqueVersion parameter to deploy
goal as deploy-file goal
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MDEPLOY-44.
------------------------------------
Assignee: Benjamin Bentmann
Resolution: Won't Fix
> 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
> 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 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
[jira] Commented: (MDEPLOY-44) Add uniqueVersion parameter to
deploy goal as deploy-file goal
Posted by "Farrukh Najmi (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128181 ]
Farrukh Najmi commented on MDEPLOY-44:
--------------------------------------
The workaround listed in previous comment would be quite adequate for me but its not working for me.
Perhaps there is a mistake in the example given?
> 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
[jira] Commented: (MDEPLOY-44) Add uniqueVersion parameter to
deploy goal as deploy-file goal
Posted by "Kalle Korhonen (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MDEPLOY-44) Add uniqueVersion parameter to deploy
goal as deploy-file goal
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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