[
https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-21791:
---------------------------------------------
[~gastaldi] I say its very crappy because no other wizards in eclipse force-saves all open
editors just because I start them.
It is not an expected behavior.
I would say if you want the minimal solution then have forge eclipse integration check if
the current editor is unsaved and ask the user if he wants to save it before he continues
(and let him save what he chooses).
Then the user will be informed about the editor needs saving for forge to work best - and
he can accept that to happen always in the future.
ps. remember to add a reset for this setting in preferences ;)
Forge addon - Changing the current file may cause a "file has
changed in file vs memory" issue in Eclipse
---------------------------------------------------------------------------------------------------------
Key: JBIDE-21791
URL:
https://issues.jboss.org/browse/JBIDE-21791
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.3.1.Beta2
Reporter: Claus Ibsen
Assignee: George Gastaldi
Fix For: 4.3.1.CR1
Attachments: eclipse-add.png
Similar problem as FORGE-2605 but this time its in Eclipse.
See the attached screenshot, where I have edited the file camel-context.xml, and then run
my forge command, which would insert a Camel endpoint at the cursor position. But eclipse
has detected a file conflict as in that dialog.
I wonder if the fix should be like in IDEA to save the file before the command is run.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)