[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Unwanted side effects from locking
The locking is done whenever a 'writable' artifact repository is accessed. In the case of HTTP, the artifact is not considered 'writable'. However, when you use a file:/ URL, a lock may be acquired. I say 'may' because we only lock on 'write' operations. However, we check for a lock on read operations (this may create the .lock file), and IIRC, we lock when we first load the repository.
We do unlock afterwards, but this doesn't appear to actually delete the file (we just give up the lock on it).
In your particular case, how do you create a lock at this location? Does your user have write access here (do they 'own' the artifacts.xml file too)?