[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-165:
------------------------------
Sprint: (was: devex #114 May 2016)
> Refactor the Connection Wizard [EBZ#492420]
> -------------------------------------------
>
> Key: ERT-165
> URL: https://issues.jboss.org/browse/ERT-165
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Refactor the connection wizard to provide:
> - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine)
> - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-165:
------------------------------
Sprint: devex #115 May 2016
> Refactor the Connection Wizard [EBZ#492420]
> -------------------------------------------
>
> Key: ERT-165
> URL: https://issues.jboss.org/browse/ERT-165
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> Refactor the connection wizard to provide:
> - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine)
> - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3882) Too much querying if Usage Reporting is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3882?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3882:
---------------------------------
Component/s: usage
> Too much querying if Usage Reporting is enabled
> -----------------------------------------------
>
> Key: JBDS-3882
> URL: https://issues.jboss.org/browse/JBDS-3882
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 8.1.0.GA
> Environment: JBDS with Teiid Designer Plugin 9.0.6.
> Windows 7 Enterprise
> Machine is locked down by domain administrators, and I do not have an admin account for full privileges.
> Reporter: Steve Tran
> Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG, Capture4.PNG
>
>
> Seems like there's a lot of querying to check if Usage Reporting is enabled. Not sure why it's taking so long, or why it needs to ask so many times. I've disabled Usage Reporting, so I would assume it would come back fast when it's set to No.
> This is something I usually ignore, but is problem-some when the clients keep pointing out how slow JBDS is because of this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3882) Too much querying if Usage Reporting is enabled
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3882?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3882:
------------------------------------
Assignee: Alexey Kazakov
> Too much querying if Usage Reporting is enabled
> -----------------------------------------------
>
> Key: JBDS-3882
> URL: https://issues.jboss.org/browse/JBDS-3882
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: usage
> Affects Versions: 8.1.0.GA
> Environment: JBDS with Teiid Designer Plugin 9.0.6.
> Windows 7 Enterprise
> Machine is locked down by domain administrators, and I do not have an admin account for full privileges.
> Reporter: Steve Tran
> Assignee: Alexey Kazakov
> Attachments: Capture.PNG, Capture2.PNG, Capture3.PNG, Capture4.PNG
>
>
> Seems like there's a lot of querying to check if Usage Reporting is enabled. Not sure why it's taking so long, or why it needs to ask so many times. I've disabled Usage Reporting, so I would assume it would come back fast when it's set to No.
> This is something I usually ignore, but is problem-some when the clients keep pointing out how slow JBDS is because of this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months