Eclipse Community Forums: Java Development Tools (JDT) » Code changes not effective in debugging after upgrading to 2.1.2

Home » Language IDEs » Java Development Tools (JDT) » Code changes not effective in debugging after upgrading to 2.1.2

Code changes not effective in debugging after upgrading to 2.1.2 [message #123038]

Sun, 30 November 2003 01:59

Eclipse User

Hi,

Previously I had not problem directly debugging new saved code changes
made in the editor without doing any rebuild; even hot code replacement
worked fine. But after I upgraded 2.1.2 last week, I now have to rebuild
the projects for any Java code changes I made; hot code replacement is not
working either. I have made no changes to my project configuration or
debug task configs, neither I have insalled any other new plug-ins.

Am I the only one seeing this? Is there a solution? Do I have to blow up
all my installation and started from fresh? or go back to 2.1.1? (BTW this
is much more painful than it should be because there is no way to export
workspace/project/task configuration to external files.)

Thank you.

Incremental compilation failed after upgrading to 2.1.2 [message #123052 is a reply to message #123038]

Sun, 30 November 2003 02:50

Eclipse User

I eventually remember this terminolgy so to update my post.

BTW I just tried blowing up all of my configurations but still doesn't
work.

Hacking Bear wrote:

> Hi,

> Previously I had not problem directly debugging new saved code changes
> made in the editor without doing any rebuild; even hot code replacement
> worked fine. But after I upgraded 2.1.2 last week, I now have to rebuild
> the projects for any Java code changes I made; hot code replacement is not
> working either. I have made no changes to my project configuration or
> debug task configs, neither I have insalled any other new plug-ins.

> Am I the only one seeing this? Is there a solution? Do I have to blow up
> all my installation and started from fresh? or go back to 2.1.1? (BTW this
> is much more painful than it should be because there is no way to export
> workspace/project/task configuration to external files.)

> Thank you.

Re: Code changes not effective in debugging after upgrading to 2.1.2 [message #123221 is a reply to message #123038]

Mon, 01 December 2003 04:06

Eclipse User

Hacking Bear wrote:
> Previously I had not problem directly debugging new saved code changes
> made in the editor without doing any rebuild; even hot code replacement
> worked fine. But after I upgraded 2.1.2 last week, I now have to rebuild
> the projects for any Java code changes I made; hot code replacement is not
> working either. I have made no changes to my project configuration or
> debug task configs, neither I have insalled any other new plug-ins.

Have you got "Workbench->Perform build automatically on resource
modification" checked in the preferences?
-tom

Previous Topic:	Eclipse Plugins Repository is down?
Next Topic:	Bind QuickFix to keystroke

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 08:51:45 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter