You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/03/30 12:18:44 UTC
[jira] Created: (MDEPLOY-28) Deployment should delete remote files
and create new ones instead of modifying them
Deployment should delete remote files and create new ones instead of modifying them
-----------------------------------------------------------------------------------
Key: MDEPLOY-28
URL: http://jira.codehaus.org/browse/MDEPLOY-28
Project: Maven 2.x Deploy Plugin
Type: Bug
Versions: 2.3
Reporter: Carlos Sanchez
Fix For: 2.3
Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
So deployment should delete metadata files and create new ones instead of editing them
--
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-28) Deployment should delete remote files
and create new ones instead of modifying them
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-28?page=all ]
Carlos Sanchez updated MDEPLOY-28:
----------------------------------
Priority: Critical (was: Major)
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: http://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 2.3
>
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
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-28) Deployment should delete remote
files and create new ones instead of modifying them
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-28?page=comments#action_66939 ]
Carlos Sanchez commented on MDEPLOY-28:
---------------------------------------
no problem
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: http://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 2.3
>
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
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-28) Deployment should delete remote
files and create new ones instead of modifying them
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-28?page=comments#action_66678 ]
John Casey commented on MDEPLOY-28:
-----------------------------------
I'd like to push this issue off until we can get wagon fixed. I don't believe it should hold up a release based on the other bugfixes in this version.
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: http://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Type: Bug
> Versions: 2.3
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 2.3
>
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
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-28) Deployment should delete remote
files and create new ones instead of modifying them
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEPLOY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276638#comment-276638 ]
Stephen Connolly commented on MDEPLOY-28:
-----------------------------------------
Is this still an issue?
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: https://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Carlos Sanchez
> Priority: Critical
> Labels: scrub-review-started
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEPLOY-28) Deployment should delete remote files
and create new ones instead of modifying them
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-28?page=all ]
John Casey updated MDEPLOY-28:
------------------------------
Fix Version: (was: 2.2.1)
2.3
pushing until wagon can be fixed and released.
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: http://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Type: Bug
> Versions: 2.2.1
> Reporter: Carlos Sanchez
> Priority: Critical
> Fix For: 2.3
>
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
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-28) Deployment should delete remote files
and create new ones instead of modifying them
Posted by "Stephen Connolly (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEPLOY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Connolly updated MDEPLOY-28:
------------------------------------
Labels: scrub-review-started (was: )
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: https://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Carlos Sanchez
> Priority: Critical
> Labels: scrub-review-started
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MDEPLOY-28) Deployment should delete remote files
and create new ones instead of modifying them
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEPLOY-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wendy Smoak updated MDEPLOY-28:
-------------------------------
Fix Version/s: (was: 2.4)
> Deployment should delete remote files and create new ones instead of modifying them
> -----------------------------------------------------------------------------------
>
> Key: MDEPLOY-28
> URL: http://jira.codehaus.org/browse/MDEPLOY-28
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Reporter: Carlos Sanchez
> Priority: Critical
>
> Remote files usually are non group writable while the directory is to prevent changes in the files without knowing who changed it (eg. apache repository policy)
> So deployment should delete metadata files and create new ones instead of editing them
--
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