[jira] Commented: (MRM-87) Place a lockfile to prevent repository operations when there is a long ongoing process

["Joakim Erdfelt (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRM-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96745 ] 

Joakim Erdfelt commented on MRM-87:
-----------------------------------

There are checks in place currently on the task/job queue side to prevent overlapping Filesystem operations.

But that doesn't take into account the file deployment issue.

Also...
* How long should the lock exist? (minutes? hours?)
* Should there be a UI provision to cleanup/force-unlock locks?
* What kind of scope should the lock have? (repository? groupId? version? artifact? etc...)
* Should the creation of locks be automatic, or manual?
* We can't reliably use java.nio Locks on OSX or Linux.  What other approach is viable?

> Place a lockfile to prevent repository operations when there is a long ongoing process
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-87
>                 URL: http://jira.codehaus.org/browse/MRM-87
>             Project: Archiva
>          Issue Type: Task
>          Components: repository interface
>    Affects Versions: 1.0
>            Reporter: John Tolentino
>            Assignee: John Tolentino
>             Fix For: Future
>
>   Original Estimate: 1 day
>  Remaining Estimate: 1 day
>
> Place a lockfile in the root of the repository that prevents deployment or other repository operations when there is a long, ongoing process.

-- 
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