March 2016 - jbosstools-issues - Jboss List Archives

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21791: ---------------------------------------- I still think we should ask the user if he/she wants to save the open and changed file. I believe that automatic saving without even asking is not that majority of Eclipse users expect. It shouldn't be hard to show a dialog asking for saving the active editor (if changed and not saved) + Don't ask again option + a setting to reset it in the preferences. > 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)

10 years, 1 month

1
0
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-21791: ------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-forge/pull/157 (was: https://github.com/jbosstools/jbosstools-forge/pull/156) > 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)

10 years, 1 month

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Lincoln Baxter III commented on JBIDE-21791: -------------------------------------------- That's OK with me. > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21835: -------------------------------- Fix Version/s: 4.3.1.CR1 > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21835 > URL: https://issues.jboss.org/browse/JBIDE-21835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master... > Deploy an eap basic app on openshift, > import the kitchensink code in the workspace > wait for the application to deploy and run on openshift > - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project. > - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to > - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard > - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink > - local change is not pushed immediately to the server. module restart happens before the change is effective. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21835: ----------------------------------- Summary: Server adapter: incremental deployment is broken Key: JBIDE-21835 URL: https://issues.jboss.org/browse/JBIDE-21835 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon Priority: Blocker Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master... Deploy an eap basic app on openshift, import the kitchensink code in the workspace wait for the application to deploy and run on openshift - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project. - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink - local change is not pushed immediately to the server. module restart happens before the change is effective. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21835) Server adapter: incremental deployment is broken

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21835: ----------------------------------- Assignee: Rob Stryker > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21835 > URL: https://issues.jboss.org/browse/JBIDE-21835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Blocker > > Running OS 3.1.1 from https://github.com/redhat-developer-tooling/openshift-vagrant/tree/master... > Deploy an eap basic app on openshift, > import the kitchensink code in the workspace > wait for the application to deploy and run on openshift > - when creating a server adapter from the OpenShift Explorer menu "Server Adapter...", on the eap service, the server has no module. The project is treated as a magic project. > - After making a change to the index page and saving, the page is incrementally pushed to the openshift server, and then the ROOT.war restart. It's not supposed to > - create a new server adapter from the Servers view. Add the kitchensink project as a module to the last page of the wizard > - jbosstools-kitchensink.war is deployed to the remote server. Both ROOT.war and jbosstools-kitchensink.war start, access to the / context root fails. It's been superseded by jbosstools-kitchensink > - local change is not pushed immediately to the server. module restart happens before the change is effective. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21386: ------------------------------------ [~mickael_istria] After pushing a significant Eclipse version change into 4.60.x TP, please remember to update the install jobs to use M5 instead of M4. Maybe we should document this step somewhere? Affected jobs: http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Create and use Neon M5 target platform > -------------------------------------- > > Key: JBIDE-21386 > URL: https://issues.jboss.org/browse/JBIDE-21386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt > > > Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Claus Ibsen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Claus Ibsen commented on JBIDE-21791: ------------------------------------- [~gastaldi] +1 > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21826) install-grinder failing (due to Central rebranding)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21826: ------------------------------------ Well.... http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... is 2/3 blue and 1/3 red (because job was not updated to use same version of Eclipse at install time as in the 4.60.x TP, which is now Neon M5). http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... has 1 blue ball out of 8. > install-grinder failing (due to Central rebranding) > --------------------------------------------------- > > Key: JBIDE-21826 > URL: https://issues.jboss.org/browse/JBIDE-21826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg > > > As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331) > But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds. > Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21826) install-grinder failing (due to Central rebranding)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21826?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21826: ---------------------------------------- I actually somehow fixed that for master yesterday, with enough success. So it should be fine. > install-grinder failing (due to Central rebranding) > --------------------------------------------------- > > Key: JBIDE-21826 > URL: https://issues.jboss.org/browse/JBIDE-21826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, install-tests > Affects Versions: 4.3.1.CR1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: central_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading...(2)_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_loading..._javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_launchbar_enabled_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_javaEE_perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg, central_not_loaded_no_gtk_installed_Resource_Perspective_testInstall(org.jboss.tools.tests.installation.InstallFromCentralTest).jpeg > > > As of Feb 4, install-grinder was mostly blue, and the occasional red ball was fixed w/ naginator. (See JBIDE-20331) > But since then, install grinder is failing again in 4.3.1.CR1 and 4.4.0.Alpha1 builds. > Not sure what's blocking the UI this time, but on the plus side, at least Red Hat Central now reports when GTK2/3 is missing on the slave. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016