[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21616:
---------------------------------------
I've checked latest nightly build of JBT 4.3.1.CR1 and it is fixed.
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3661:
--------------------------------
Summary: Remove VAGRANT_DETECTED_OS from env variables in CDK launch config on Windows (was: Remove VAGRANT_DETECTED_OS from env variables in CDK launch config)
> Remove VAGRANT_DETECTED_OS from env variables in CDK launch config on Windows
> -----------------------------------------------------------------------------
>
> Key: JBDS-3661
> URL: https://issues.jboss.org/browse/JBDS-3661
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, server
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> With mingw based ssh/rsync this env varibale is not required.
> It is also set in windows user env variables, so there is no reason to duplicate that anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[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 commented on JBIDE-21816:
---------------------------------------
[~snjeza] if you are experiencing this issue on Ubuntu with GTK 3.18, please reopen this issue.
> 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
[JBoss JIRA] (JBIDE-19977) Multiple download windows blinking for intermediate images while pulling from docker registry
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19977?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19977.
---------------------------------
Verified in latest JBDS 9.1.0.CR1 build - it uses Docker 1.2.1:
org.eclipse.linuxtools.docker.feature_1.2.1.201602162146
> Multiple download windows blinking for intermediate images while pulling from docker registry
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-19977
> URL: https://issues.jboss.org/browse/JBIDE-19977
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> In Docker Tooling, after establishing a connection to my local boot2docker instance, I tried to pull jboss/wildfly in the Docker Images view.
> This worked, but the UI was not very nice. To get the WildFly image, Docker needs to download about 30 intermediate images. For each image, a download window would open for a short period of time and then close again.
> The overall progress is visible in the status bar of Eclipse, but otherwise you get multiple download windows opening and closing again, which is very distracting and you can't really do any other work in the meantime since a newly opened window will interrupt you again anyway. (Overall, it takes me several minutes to download the wildfly image for the first time.)
> I think a better approach would be to have one window for all the images being downloaded combined.
> Upstream BZ is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469627
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21927) Collect usage on LiveReload
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-21927:
-------------------------------------
Summary: Collect usage on LiveReload
Key: JBIDE-21927
URL: https://issues.jboss.org/browse/JBIDE-21927
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: livereload
Affects Versions: 4.3.1.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
Fix For: 4.3.1.CR1
Measure number of installations, LiveReload server starts and maybe even number of requests, grouped by day.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3697) Installed vagrant version in not validated against anything
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3697?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-3697:
---------------------------------
Assignee: Denis Golovin
> Installed vagrant version in not validated against anything
> -----------------------------------------------------------
>
> Key: JBDS-3697
> URL: https://issues.jboss.org/browse/JBDS-3697
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> It looks like the installer stores the version of a vagrant installation it finds/the user selects, but there is no value it would check it against. (Which is strange because I remember putting it into the code and the html file still references the fields which apparently don't exist anymore).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years