March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21705) update tools.jboss.org/usage with error reporting tracking details

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21705?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21705: ---------------------------------------- Do we have a text for it? > update tools.jboss.org/usage with error reporting tracking details > ------------------------------------------------------------------ > > Key: JBIDE-21705 > URL: https://issues.jboss.org/browse/JBIDE-21705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, usage > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > usage page should not just talk about Google analytics, but aslo about error reporting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-3664: ----------------------------------------- Summary: Do we still need/want custom build of vagrant ? Key: JBDS-3664 URL: https://issues.jboss.org/browse/JBDS-3664 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: installer Reporter: Max Rydahl Andersen Priority: Blocker we seem to install use our custom vagrant build. Is that still relevant ? With that we need to test much more since our build could be different. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3663) Use URL redirects for vagrant and VirtualBox

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3663?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3663: --------------------------------- Labels: havoc (was: ) > Use URL redirects for vagrant and VirtualBox > -------------------------------------------- > > Key: JBDS-3663 > URL: https://issues.jboss.org/browse/JBDS-3663 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > In case the third parties change their download locations, we should use URL redirects, and not directly embed the download URLs in to our downloader -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3663) Use URL redirects for vagrant and VirtualBox

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/JBDS-3663?page=com.atlassian.jira.plugin.... ] Pete Muir commented on JBDS-3663: --------------------------------- For example we call developers.redhat.com/redirect/to/virtualbox.download which would issue a 307 to the actual Oracle URL > Use URL redirects for vagrant and VirtualBox > -------------------------------------------- > > Key: JBDS-3663 > URL: https://issues.jboss.org/browse/JBDS-3663 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > > In case the third parties change their download locations, we should use URL redirects, and not directly embed the download URLs in to our downloader -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21816: ----------------------------------------------- gtk3 3.10.8-0ubuntu1.4 i386 > 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 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3663) Use URL redirects for vagrant and VirtualBox

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3663?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3663: --------------------------------- Fix Version/s: 9.1.0.CR1 > Use URL redirects for vagrant and VirtualBox > -------------------------------------------- > > Key: JBDS-3663 > URL: https://issues.jboss.org/browse/JBDS-3663 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Pete Muir > Priority: Critical > Fix For: 9.1.0.CR1 > > > In case the third parties change their download locations, we should use URL redirects, and not directly embed the download URLs in to our downloader -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3663) Use URL redirects for vagrant and VirtualBox

by Pete Muir (JIRA)

Pete Muir created JBDS-3663: ------------------------------- Summary: Use URL redirects for vagrant and VirtualBox Key: JBDS-3663 URL: https://issues.jboss.org/browse/JBDS-3663 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Reporter: Pete Muir Priority: Critical In case the third parties change their download locations, we should use URL redirects, and not directly embed the download URLs in to our downloader -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21816: ------------------------------------------ [~snjeza] thanks! [~scabanovich] can you report your GTK3 version please? > 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 month

1
0
0 / 0

[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: --------------------------------------- I am testing the issue. I suppose it is similar to the issue described in JBIDE-21072. What version of GTK3 are you using? > 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21761: --------------------------------------- We control this particular case so whether we limit you to numeric values is up to us, but the fact is you can have numeric or named ports. It's more of an issue where we are reading information sourced elsewhere. I would defer to allowing either which means the current PR will need to be reverted in some capacity. > Port mapping validation is not correct > -------------------------------------- > > Key: JBIDE-21761 > URL: https://issues.jboss.org/browse/JBIDE-21761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: validation_msg.png > > > In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image. > !validation_msg.png! > There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible. -- 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