| My External Tools command is no longer saving dirty editors in Eclipse 3.2 [message #306001] |
Mon, 17 July 2006 16:46  |
Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I recently upgraded from Eclipse 3.1 to Eclipse 3.2 and I ran into an
annoying difference in behavior.
In Eclipse 3.1 when I would make a change to my Ant script and then
click on the External Tool I set up that runs the Ant script, Eclipse
would automatically save all the dirty editors before running the
External Tool. After the upgrade, Eclipse 3.2 will not save the dirty
editors before running the External Tool. I can not find a setting under
Windows Preferences or under External Tools that influences this behavior.
I have the "Save required dirty editors before launching" option set
under Run/Debug -> Launching. I also have "Save automatically before
build" set under General -> Workspace but these options don't have an
effect on the behavior when I select the External Tool. Eclipse does
save dirty editors as expected when I select "Build All" from the
project menu.
Is anybody else having a problem with this? Was the behavior changed on
purpose? Is there a setting which can restore the 3.1 behavior?
John Aronson
|
|
|
|
| Re: My External Tools command is no longer saving dirty editors in Eclipse 3.2 [message #306312 is a reply to message #306143] |
Wed, 26 July 2006 13:35  |
| Eclipse User |
|
|
|
I'm having this problem, too. I've read the bug report, and I don't, yet,
if we are extending LaunchConfigurationDelegate. (The person who write it
no longer works here.) But before I go investigating, I wanted to ask:
If I change this, do I have to change it to be an Eclipse 3.2 only version
of our product, or will the changed one continue to work correctly in
Eclipse 3.1?
Thanks in advance.
|
|
|
Powered by
FUDForum. Page generated in 0.27794 seconds
Home