[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

Lars Heinemann (JIRA) issues at jboss.org
Tue Mar 1 10:30:03 EST 2016


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

Lars Heinemann edited comment on JBIDE-21791 at 3/1/16 10:29 AM:
-----------------------------------------------------------------

Hard to say without any steps on how to reproduce that issue. I have also no clue how the forge command works here. Probably its related to the forge command even. Need more input. Keep in mind that we use the default xml editor for our editor. So there is no magic voodoo we do here especially for Fuse Tooling.


was (Author: lhein):
Hard to say without any steps on how to reproduce that issue. I have also no clue how the forge command works here. Probably its related to the forge command even. Need more input.

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


More information about the jbosstools-issues mailing list