|Re: classpath issue [message #835584 is a reply to message #835571]
||Tue, 03 April 2012 12:27
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 2012.04.03 6:11, Jay krish wrote:|
> classpath file is NOT read-only and checked out in Clear Case. Even then
> I get the error message that the file is read only, while trying to
> add/remove jars in "java build path"
> I am new to Eclipse environment, Can anyone please help me know the
> importance of .classpath file. How it will be useful? :d
This file lists all the JARs that support your project and performs some
other tasks such as supply links to Javadoc for those JARs that you set
up if in coding you wish to see more usefully the interfaces therein or,
when debugging, wish to step debug down inside them.
The JARs are thereby considered to be "on your class path" for the
purpose of compilation, but as I noted above, also for the Editor's use
(Content Assist, what Visual Studio calls Intellisense) and the
When you are in Build Path -> Configure Build Path -> Libraries (tab)
and making changes, Eclipse needs write access to this file.
Powered by FUDForum
. Page generated in 0.02664 seconds