Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

.classpath is read only

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I am trying to add a external class folder to my existing project. When I try to do that I get this error .classpath is read only . I tried looking around for solutions and in most places I found that may be the eclipse_classpath.xml is read only. I was syncing this original project from a version control system and then trying to add another folder from the version control system as well. I first checked out the classpath file and change the file permission from read only to writable. Then when I imported this in eclipse and try to add an external folder by going under configure build path I get the error saying .classpath is read only. After that I went in eclipse to check the permission on the file. I see that read only flag was disable which looks fine to me. I do see 2 other options there one is Archive and other one is Derived that are unchecked as well. I am not sure what am I doing wrong here? Can someone please advice.

Thanks in advance!!!
 
Ranch Hand
Posts: 859
IBM DB2 Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
.classpath is built by Eclipse when you change the Project Build Path.

for example each developer may have their own workspace etc., so .classpath should not be in version control! (like target)

You should not be tweaking this file manually!

Also, it could be read-only due to version control checkout or other issues.

WP
 
N Tiwa
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

Thanks for your reply. I did copy the whole project separately and again it has the same issues. Any suggestions??

Thanks in advance!
 
William P O'Sullivan
Ranch Hand
Posts: 859
IBM DB2 Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Even if you copied everything, you may still have the .classpath set to "read-only".

Set the attributes to read-write, then Eclipse will update it when you change the classpath.

Again be careful if you commit that file back to source control! (Which should be ignored anyway)

WP
 
I am not a spy. Definitely. Definitely not a spy. Not me. No way. But this tiny ad ...
We need your help - Coderanch server fundraiser
https://coderanch.com/t/782867/Coderanch-server-fundraiser
reply
    Bookmark Topic Watch Topic
  • New Topic