This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The .classpath file is created by eclipse and is used to keep track of the classpath needed to build your project in eclipse. Adding external files to a project tells eclipse it needs to add new entries to the classpath, and if the .classpath file *is* read-only, then eclipse can't write these new entries to the .classpath file.
The solution, change .classpath not to be read only. You can do this either through your OS, or through eclipse itself (but you'll have to open resource perspective, because .classpath is filtered out of the file-list by default in the Java view - Window -> Open Perspective -> Other... -> Resource -> OK; Right click the .classpath file in the Navigator tab -> Properties -> Uncheck "Read Only" -> OK).
Or there may be other reasons why .classpath is read only... was this project checked out from a version control system? If so, you need to "check out" the .classpath file first to allow your version control system to change it from "read only".
Write once, run anywhere, because there's nowhere to hide! - /. A.C.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com