March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21816: --------------------------------------- {quote} if you are experiencing this issue on Ubuntu with GTK 3.18, please reopen this issue. {quote} I can't reproduce the issue described in this jira. {quote} It is reproducible on Ubuntu with GTK 3.18. {quote} This is related to JBIDE-21038. > Table is not refreshed properly in SWT_GTK3 > ------------------------------------------- > > Key: JBIDE-21816 > URL: https://issues.jboss.org/browse/JBIDE-21816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > This issue was found while testing JBIDE-21815 and description to that issue fits to what happens in SWT_GTK3 with table. Difference is that the other issue is caused by some model failures and can be reproduced on all OS, and this case is relevant only to SWT_GTK3 when wizard model works without failures. > Steps for some generic wizard (Deploy Image to Openshift is an example). > 1. Create a wizard with two pages. First page has some text input, second table. Content of table is refreshed on change of text input on the first page. Input object for the table is the same, only content provider returns new values. Table has scroll, and content should be large enough to make scroll appear (without scroll, the issue is not reproduced). > 2. Change text input on the first page, and push 'Next->' to open the second page. > 3. At the very first navigating to the second page, the content of the table is correct, as provided by the logic binding the text input and the table. > 4. Go back to the first page and change text input. > 5. Again navigate to the second page. > 6. Failure - content of the table remains as it was for the previous text input. > 7. Recovering - just pass mouse over the table, its data in cells passed is refreshed. That means that table model is refreshed, but rendering was not completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21923: ---------------------------------- Description: In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. (was: See JBIDE-21645 for more details) > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Enhance import of OpenShift applications

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21923: ------------------------------------- Do you mind adding the details in this ticket? > Enhance import of OpenShift applications > ---------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.4.x > > > See JBIDE-21645 for more details -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21931) Link with Editor does not work on Windows

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-21931: ---------------------------------- Summary: Link with Editor does not work on Windows Key: JBIDE-21931 URL: https://issues.jboss.org/browse/JBIDE-21931 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.3.1.CR1 Reporter: Pavol Srna Fix For: 4.3.1.CR1 Link with Editor does not work on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21929: ------------------------------------- Summary: Server adapter: incremental deployment is broken Key: JBIDE-21929 URL: https://issues.jboss.org/browse/JBIDE-21929 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 Issue #1 - 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 Issue #2 - 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. (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21930) Liberalize some astools API for re-use

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21930: ------------------------------------- Summary: Liberalize some astools API for re-use Key: JBIDE-21930 URL: https://issues.jboss.org/browse/JBIDE-21930 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.3.1.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.3.1.CR1 In order to allow openshift to use (but also override pieces of) our incremental deployment, we must liberalize a few methods from private to protected, and add a few superclasses for extending to avoid code duplication. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21929?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21929: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21929 > URL: https://issues.jboss.org/browse/JBIDE-21929 > 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.4.0.Alpha1 > > > 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 > Issue #1 > - 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 > Issue #2 > - 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. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21929?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21929. ----------------------------------- Resolution: Done > Server adapter: incremental deployment is broken > ------------------------------------------------ > > Key: JBIDE-21929 > URL: https://issues.jboss.org/browse/JBIDE-21929 > 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.4.0.Alpha1 > > > 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 > Issue #1 > - 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 > Issue #2 > - 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. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21835?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21835. --------------------------------- Ok. Verified on nightly build of JBT with OpenShift plugin build B240. > 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 > Issue #1 > - 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 > Issue #2 > - 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. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 resolved JBIDE-21835. --------------------------------- Resolution: Done AFAIK, this is the only way to ensure the remote server is in sync with the local content. So even though the initial cost might seem heavy, I think this is a win on long term usage. Resolving then. > 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 > Issue #1 > - 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 > Issue #2 > - 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. > (Fred indicates this issue was not replicatable on most recent test) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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