[JBoss JIRA] (FORGE-2605) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDAE - forge-issues

Friday, 26 February 2016

    [
https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin...
] 

Claus Ibsen commented on FORGE-2605:
------------------------------------

So in the source code I added .wireTap and then invoked the command. And as you can see
the difference is that the command added the Camel endpoint in the old source code.

So I wonder if IDEA save the code changes you do in the editor "delayed". So we
may want to have a command / api in forge that forge developers can trigger IDEA to save
to disk, so we work on 100% latest code.

...
 Forge addon - Changing the current file may cause a "file has
changed in file vs memory" issue in IDAE

------------------------------------------------------------------------------------------------------

                 Key: FORGE-2605
                 URL: https://issues.jboss.org/browse/FORGE-2605
             Project: Forge
          Issue Type: Bug
    Affects Versions: 3.0.0.CR1
            Reporter: Claus Ibsen
         Attachments: Screen Shot 2016-02-26 at 1.53.40 PM.png, Screen Shot 2016-02-26 at
1.56.01 PM.png

 We have a set of forge commands that changes the source code, such as adding or editing
Camel endpoints.
 Sometimes when running those commands, and the command is success. Then IDAE has detected
a diff between the source in memory vs file, and it shows a dialog (see screenshot).

--
This message was sent by Atlassian JIRA
(v6.4.11#64026)

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

[JBoss JIRA] (FORGE-2605) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDAE