qiulong / jupiter-eclipse-plugin

Automatically exported from code.google.com/p/jupiter-eclipse-plugin
0 stars 0 forks source link

Editing the review properties with a read-only .jupiter file does not produce a warning indicating a read-only file #111

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Checkout a project from SVN
2. The .jupiter file has the SVN property svn:needs-lock * so that everyone
has to use the lock-modify-unlock process for this configuration file. 
Yeah, I realize it is xml but it makes it easier overall if we don't have 
to merge changes.
3. The file was read-only (part of the svn:needs-lock) and I thought I had 
grabbed the lock but I didn't. I went in and made many changes (added 
files) and thought my changes were made.
4. I later went back into the properties/review and noticed that none of my 
changes were made.

What is the expected output? What do you see instead?
I would have expected an error message indicating that the file was not 
writable.

What version of the product are you using? On what operating system?
Jupiter Feature 3.5.1/WinXP 32bit

Which Eclipse bundle do you have?
A. Eclipse IDE for Java EE Developers
B. Eclipse IDE for Java Developers
C. Eclipse for PHP Developers
D. Eclipse IDE for C/C++ Developers
E. Eclipse for RCP/Plug-in Developers
F. Eclipse IDE for Java and Report Developers
G .Eclipse Classic
H. Other (Please specify)

Eclipse Classic 

Please provide any additional information below.

Original issue reported on code.google.com by dustinb...@gmail.com on 4 May 2010 at 8:10

GoogleCodeExporter commented 9 years ago
Are you able to attach the log file for this?  I believe there should be an 
entry in the log file if it failed to write to any of the files.

Original comment by jsakuda on 18 Jan 2011 at 5:44