[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
Max Rydahl Andersen (JIRA)
issues at jboss.org
Wed Mar 2 03:15:02 EST 2016
[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170552#comment-13170552 ]
Max Rydahl Andersen commented on JBIDE-21791:
---------------------------------------------
So you suggest that anytime I start a forge command forge will force a save all on every open editor ?
I find that very crappy and a very leaky abstraction.
Could it be done only for resources that gets opened for editing ?
> 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)
More information about the jbosstools-issues
mailing list