Thanks Tom, I hadn't refined my Bugzilla search enough to see that one. So that jvm argument will allow you to turn off artifact locking in M7, but where am I with M6? Is there any way I can get M6 to work on my local read only repositories?
Thanks, Terry On Fri, Apr 29, 2011 at 5:50 AM, Thomas Watson <[email protected]> wrote: > Because of these types of issues we decided to disable the artifact locking > by default (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=341826). In > M6 the locking was enabled by default. > > Tom > > > > [image: Inactive hide details for Terry Parker ---04/29/2011 01:16:21 > AM---I'm late to this thread, but I'm doing some work to setup a]Terry > Parker ---04/29/2011 01:16:21 AM---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 ev > > > From: > Terry Parker <[email protected]> > To: > P2 developer discussions <[email protected]> > Date: > 04/29/2011 01:16 AM > Subject: > Re: [p2-dev] Talk'n Lock'n > ------------------------------ > > > > 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). > > Thanks, > Terry > > > > On Tue, Apr 5, 2011 at 6:57 AM, Oberlies, Tobias <*[email protected] > * <[email protected]>> wrote: > > > > 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?). > > 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". > > Best regards > Tobias > _______________________________________________ > p2-dev mailing list* > **[email protected]* <[email protected]>* > > **https://dev.eclipse.org/mailman/listinfo/p2-dev*<https://dev.eclipse.org/mailman/listinfo/p2-dev> > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > > > > _______________________________________________ > p2-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/p2-dev > >
<<graycol.gif>>
<<ecblank.gif>>
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
