February 2016 - forge-issues - Jboss List Archives

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

by Claus Ibsen (JIRA)

Claus Ibsen created FORGE-2606: ---------------------------------- Summary: Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse Key: FORGE-2606 URL: https://issues.jboss.org/browse/FORGE-2606 Project: Forge Issue Type: Bug Affects Versions: 3.0.0.CR1 Reporter: Claus Ibsen 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)

9 years, 6 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-2605. ---------------------------------- Fix Version/s: 3.0.0.CR2 Assignee: George Gastaldi Resolution: Done Fixed in the IDEA plugin > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDEA > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-2605 > URL: https://issues.jboss.org/browse/FORGE-2605 > Project: Forge > Issue Type: Bug > Components: UI - IntelliJ IDEA > Affects Versions: 3.0.0.CR1 > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 3.0.0.CR2 > > 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)

9 years, 6 months

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-2605: ----------------------------------- Component/s: UI - IntelliJ IDEA > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDEA > ------------------------------------------------------------------------------------------------------ > > Key: FORGE-2605 > URL: https://issues.jboss.org/browse/FORGE-2605 > Project: Forge > Issue Type: Bug > Components: UI - IntelliJ IDEA > 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)

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] Claus Ibsen commented on FORGE-2605: ------------------------------------ So basically I want something a like file -> save all in IDEA to run before I do code changes in the source code. Or somehow be able to load the source using IDEA api where IDEA can provide me with the latest memory source code. It may be that the file api in forge loads from disk, and don't know about memory changes pending from IDEA. So maybe forge need to hook into IDEA somehow? But I can settle with a api in forge that forces IDEA (and Eclipse if running in Eclipse etc) to save all, then I can invoke that before I do code changes using my commands. > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDEA > ------------------------------------------------------------------------------------------------------ > > 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)

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

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

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] Claus Ibsen updated FORGE-2605: ------------------------------- Summary: Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDEA (was: Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDAE) > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in IDEA > ------------------------------------------------------------------------------------------------------ > > 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)

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] Claus Ibsen updated FORGE-2605: ------------------------------- Attachment: Screen Shot 2016-02-26 at 1.56.01 PM.png > 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)

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

Claus Ibsen created FORGE-2605: ---------------------------------- Summary: 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 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)

9 years, 6 months

1
0
0 / 0

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

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2605?page=com.atlassian.jira.plugin... ] Claus Ibsen updated FORGE-2605: ------------------------------- Attachment: Screen Shot 2016-02-26 at 1.53.40 PM.png > 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 > > > 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)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (FORGE-2604) IDEA/Eclipse development - Make it possible to log to log/eventlog

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/FORGE-2604?page=com.atlassian.jira.plugin... ] Claus Ibsen updated FORGE-2604: ------------------------------- Attachment: error.png Screenshot error.png of IDAE event log when I run a forge command and it failed. All I can see is that single red line about a string index out of bounds error. > IDEA/Eclipse development - Make it possible to log to log/eventlog > ------------------------------------------------------------------ > > Key: FORGE-2604 > URL: https://issues.jboss.org/browse/FORGE-2604 > Project: Forge > Issue Type: Feature Request > Components: UI - API > Affects Versions: 3.0.0.CR1 > Reporter: Claus Ibsen > Attachments: error.png > > > Developing forge addons is really painful when developing and testing for GUIs such as IDEA or Eclipse. > There is no logging or visibility what happens. And logging on IDEA or Eclipse is different, and you as a forge addon developed dont really know where the log files of IDEA/Eclipse are stored and how to log to them. > Forge should have an easy API that you can use to > - log in IDEA/Eclipse log > - log to custom log file which you can easily configure > - log to IDEA/Eclipse event log / console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2016