Skip to main content



      Home
Home » Newcomers » Newcomers » How shall we avoid occuring class file editor?(class editor)
icon1.gif  How shall we avoid occuring class file editor? [message #1146828] Sun, 20 October 2013 08:36 Go to next message
Eclipse UserFriend
when debug a file, occasionallly pop up a class file editor and warning, source not found.
then it will ask you for change atteched source...

after all we have jar package, but not often have their source codes in the ide.
How shall we avoid this situation taking place when we debug a class?
Re: How shall we avoid occuring class file editor? [message #1147640 is a reply to message #1146828] Sun, 20 October 2013 21:39 Go to previous messageGo to next message
Eclipse UserFriend
Do we have any method except using F6?
Re: How shall we avoid occuring class file editor? [message #1148479 is a reply to message #1147640] Mon, 21 October 2013 10:36 Go to previous messageGo to next message
Eclipse UserFriend
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
settings.

Bonus

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.
Re: How shall we avoid occuring class file editor? [message #1150073 is a reply to message #1148479] Tue, 22 October 2013 10:14 Go to previous message
Eclipse UserFriend
thank very much, very helpful,
and
how to expand the 3party jar? It insists on requiring source java files when debug, use jd-gui to decompile those the 3rd-jar?
or how to find the positoin of the source jars?

would you pls detail any more?

[Updated on: Tue, 22 October 2013 22:07] by Moderator

Previous Topic:"only include exported entries" not saved
Next Topic:How Do you Set Juno (eclipse IDE) to Debug Mode
Goto Forum:
  


Current Time: Sat Jul 05 23:44:49 EDT 2025

Powered by FUDForum. Page generated in 0.08506 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top