Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339178 - IOException when we try to acquire a lock in a read only area
Summary: IOException when we try to acquire a lock in a read only area
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Ian Bull CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 04:05 EST by Ian Bull CLA
Modified: 2011-03-08 15:15 EST (History)
1 user (show)

See Also:

Attachments
Patch v1 (8.23 KB, patch)
2011-03-08 14:52 EST, Ian Bull CLA 		no flags Details | Diff
mylyn/context/zip (97.25 KB, application/octet-stream)
2011-03-08 14:52 EST, Ian Bull CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Bull CLA 2011-03-08 04:05:45 EST 
When we try to acquire the artifact repository lock in a read only area, we get an IOException.  We need to handle this case.
Comment 1 Ian Bull CLA 2011-03-08 14:52:05 EST 
Created attachment 190686 [details]
Patch v1

This patch now checks if the location is 'read only' and sets the appropriate flag. If the location is read only, then we assume the area can't be locked, and we don't try -- same thing we do for a repository that cannot be modified.
Comment 2 Ian Bull CLA 2011-03-08 14:52:08 EST 
Created attachment 190687 [details]
mylyn/context/zip
Comment 3 Ian Bull CLA 2011-03-08 15:15:41 EST 
I've released this fix to head.