[jbosstools-issues] [JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

[Claus Ibsen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173696#comment-13173696 ] 

Claus Ibsen commented on JBIDE-21791:
-------------------------------------

Maybe the forge command can have some details what it requires.

So in my commands its only the current file in the editor that matters. Any other open files that is unsaved I do not touch.
So maybe the command can have a way of saying that its editing the current file, and therefore forge should ensure the file is saved first.



> 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)