[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Talk'n Lock'n
- From: Terry Parker <tparker@xxxxxxxxxx>
- Date: Thu, 28 Apr 2011 23:15:17 -0700
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=Y2X9LVaZGDbc7GXHrKSOsveLdrLe1Wfy2eCKj2IcgTI6oIrk3fZUlpuo6INNfMZ9kA yQ9xn5B1U+PvN7C147cg==
I'm late to this thread, but I'm doing some work to setup a distribution based on 3.7m6, and I'm getting lock-related errors everywhere when I point to repos with file-based URIs. Mainly I get errors like this:
java.io.IOException: The folder "/home/eclipse/repos/checkstyle/5.3.1/.artifactlock/.metadata" is read-only.
I'm not sure why that is, since I have write permission to that folder, but most of my users won't. The environment here is Linux.
I suspect that I should be setting my repositories as read only but I didn't find any documentation to do that (I only ever do headless p2 operations to create repositories).
On Tue, Apr 5, 2011 at 6:57 AM, Oberlies, Tobias <tobias.oberlies@xxxxxxx>
What is the use case of changing the shape? I can't imagine why you'd want to do that. Locking is a very useful feature, and if mutable shape is blocking a good solution, just drop that "feature".
Ian Bull wrote:
> 4. Don't use .lock files, but instead use the artifacts.jar as the lock
> file. This seems like the best solution and I've spent some time this
> weekend prototyping it. There are a few challenges with this approach that
> may be show stoppers (we allow users to change the 'shape' of the
> repository -- from .jar to .xml. This means that the .lock file will
> suddenly change; how do we deal with this? Also, what comes first, the
> repository or the lock?).