Community
Participate
Working Groups
In case we're not happy with the artifact locking, we should provide an easy way to disable it.
I'm implementing this with a VM args -Declipse.p2.artifact.locking. By default this is true. If you specify false, then no locking will be done. We may want to make this 'per agent', but since agents aren't named, this might be tricky.
Created attachment 192494 [details] Patch v1 This provides a VM arg to control the locking of artifact repositories.
Created attachment 192495 [details] mylyn/context/zip
Created attachment 192500 [details] Patch v2 This now sets locking 'false' by default. This also enables locking during the test cases which test the artifact locking.
Created attachment 192501 [details] mylyn/context/zip
Created attachment 192504 [details] Patch v3 This makes the property name 'uglier': eclipse.p2.internal.simple.artifact.repository.locking
Created attachment 192505 [details] mylyn/context/zip
I've released this. For now the value is 'true' by default.
you might consider leaving this bug open. As I understand it, we wanted the value false by default. Either that or open another bug to ensure that we change it before shipping. Would also mark it as high priority so we don't forget.
done.
false by default.