|Re: How shall we avoid occuring class file editor? [message #1148479 is a reply to message #1147640]
||Mon, 21 October 2013 14:36
| Russell Bateman
Registered: July 2009
Location: Provo, Utah, USA
On 10/20/2013 7:39 PM, Zhg Mising name wrote:|
> Do we have any method except using F6?
In the Libraries tab of the Build Path dialog, you can expand each of
the third-party JARs you're consuming where you'll then find Source and
Javadoc. If you get source JARs, you can easily attach them in this way.
The other option is to tell Eclipse the path to the top of source
folders if you have them on disk. Once you do this, you'll be able to
debug down inside the source.
Content Assist works this way too. If you get source or Java doc JARs,
you can easily attach them. The other option is to tell Eclipse the path
to the top of source folders or folders containing Javadoc. Once you do
this, you'll get Eclipse Content Assist when you wave the mouse over an
indentifier in your code or perform other actions depending on your
If you can, elect to edit these paths "in the workspace"--in fact, in
the project itself (so, drop and link to the source or Javadoc JARs
inside your project). If you don't do this, your .classpath file will no
longer be portable to other computers. This is a real problem if you're
sharing your project via version control with colleagues or even working
on the project yourself on two different computer hosts.
Hope this helps.
Powered by FUDForum
. Page generated in 0.03901 seconds