April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-624) Fixed XmlSchemalessTest, Added SAP Hana import tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-624?page=com.atlassian.jira.plugin.... ] stanislav kaleta resolved JBTIS-624. ------------------------------------ Resolution: Done > Fixed XmlSchemalessTest, Added SAP Hana import tests > ----------------------------------------------------- > > Key: JBTIS-624 > URL: https://issues.jboss.org/browse/JBTIS-624 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.2.6.CR2, 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21816. --------------------------------- Was not able to reproduce on nightly build of JBT, it seems to be fixed. > 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 > > > 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-22061) Table is not refreshed properly in SWT_GTK3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22061?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22061: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Table is not refreshed properly in SWT_GTK3 > ------------------------------------------- > > Key: JBIDE-22061 > URL: https://issues.jboss.org/browse/JBIDE-22061 > 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.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-22061) Table is not refreshed properly in SWT_GTK3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22061?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-22061. ----------------------------------- Resolution: Done > Table is not refreshed properly in SWT_GTK3 > ------------------------------------------- > > Key: JBIDE-22061 > URL: https://issues.jboss.org/browse/JBIDE-22061 > 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.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] (JBTIS-624) Fixed XmlSchemalessTest, Added SAP Hana import tests

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-624?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-624: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/676 > Fixed XmlSchemalessTest, Added SAP Hana import tests > ----------------------------------------------------- > > Key: JBTIS-624 > URL: https://issues.jboss.org/browse/JBTIS-624 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22061: ------------------------------------- Summary: Table is not refreshed properly in SWT_GTK3 Key: JBIDE-22061 URL: https://issues.jboss.org/browse/JBIDE-22061 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-21816) Table is not refreshed properly in SWT_GTK3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21816: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > 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 > > > 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-21603) CDK Runtime is useless stub and should be removed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21603. --------------------------------- Confirmed in JBDS 9.1.0.CR1 B443. There is no mention of runtimes in relation to cdk anywhere anymore. > CDK Runtime is useless stub and should be removed > ------------------------------------------------- > > Key: JBIDE-21603 > URL: https://issues.jboss.org/browse/JBIDE-21603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens. > 1. Create a cdk server > 2. Open the new server dialog again > 3. For server type, select CDK > 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens > At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor. > When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog. > So it seems we're somewhere halfway between not using runtimes at all and using them to some degree. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3552. ------------------------------- There is actually nothing new in Docker Tooling for this - I did use volume mounting in the demo we did for DevConf in Brno back in February. Unfortunately cdk still does not support volume mounting in the docker that's included. But that's a known limitation for now. Closing this issue. > Developer - be able to incrementally deploy changes to docker containers > ------------------------------------------------------------------------- > > Key: JBDS-3552 > URL: https://issues.jboss.org/browse/JBDS-3552 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: docker, openshift > Reporter: Max Rydahl Andersen > Assignee: Martin Malina > Priority: Critical > Fix For: 9.1.0.CR1 > > > User Story: > As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly. > Acceptance Criteria: > * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment. > * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh. > * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source) > * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22060) Preferences: openshift 3 oc location is saved on cancel, validation is broken

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22060: ------------------------------------- Summary: Preferences: openshift 3 oc location is saved on cancel, validation is broken Key: JBIDE-22060 URL: https://issues.jboss.org/browse/JBIDE-22060 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.1.CR1, 4.4.0.Alpha1 Validation should show/clean error message and update OK and Apply buttons on each change. Now, error message and button state is updated only after input text field looses focus. Cancel should leave value that was saved at the last OK or Apply or Perform Defaults (let Perform Defaults apply its value even if it is not correct). Now, after changing input and cancelling, when preferences dialog is reopened, the value is changed. -- 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 April 2016