[JBoss JIRA] (JBIDE-25161) Unify "Deprecated" tags in Central's Software/Update Tab
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-25161:
-------------------------------------
Summary: Unify "Deprecated" tags in Central's Software/Update Tab
Key: JBIDE-25161
URL: https://issues.jboss.org/browse/JBIDE-25161
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: central
Affects Versions: 4.5.1.AM3
Reporter: Josef Kopriva
Please unify "Deprecated" tag in available features.
E.g.: JBoss Tools SwitchYard has "(DEPRECATED)" in name, but not in description, JBoss Arquillian has "(Deprecated)" only in description, JBoss OpenShift 2 Tools has "(Deprecated)" in name and in description.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25160) Unknown category 'com.jboss.jbds.discovery.certification.supported'
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-25160:
-------------------------------------
Summary: Unknown category 'com.jboss.jbds.discovery.certification.supported'
Key: JBIDE-25160
URL: https://issues.jboss.org/browse/JBIDE-25160
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.5.1.AM3
Reporter: Josef Kopriva
Assignee: Nick Boldt
An error is shown when I switch to Software/Update Tab of Central:
{code:java}
eclipse.buildId=11.1.0.AM3-v20171005-1232-B1225
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.devstudio.core.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.eclipse.mylyn.discovery.core
Error
Fri Oct 06 16:39:35 CEST 2017
Unknown category 'com.jboss.jbds.discovery.certification.supported' referenced by connector 'jboss.integration-stack.bundle.switchyard' declared in com.jboss.jbds.central.discovery.integration_stack_11.0.0.GA_v20170811_1249_B41.jar_8615146590590774369.jar
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBDS-3756) Have two progress bars download and installation progress
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ]
Mohit Suman edited comment on JBDS-3756 at 10/6/17 9:50 AM:
------------------------------------------------------------
Based on the development team discussion, we have come up with a *Single Progress Bar* for all _components_ selected for download.
Currently, every component has its own Progress bar showing the Download and Install status respectively. But as the components keep on increasing, it is not a feasible approach to display on the UI. We have made a Single Progress bar of the Download & Installation for all components selected by the user.
[~crobson] Please review and let me know if any changes needed. I have attached the video for the new progress bar UI. https://vimeo.com/237079791
was (Author: msuman):
Based on the development team discussion, we have come up with a *Single Progress Bar* for all _components_ selected for download.
Currently, every component has its own Progress bar showing the Download and Install status respectively. But as the components keep on increasing, it is not a feasible approach to display on the UI. We have made a Single Progress bar of the Download & Installation for all components selected by the user.
[~crobson] Please review and let me know if any changes needed. I have attached the video for the new progress bar UI.
> Have two progress bars download and installation progress
> ---------------------------------------------------------
>
> Key: JBDS-3756
> URL: https://issues.jboss.org/browse/JBDS-3756
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Pete Muir
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
>
> Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now.
> Update:
> After discussion on backlog grooming session it seems reasonable to have two progress bars instead of one. Considering size of downloaded resources and time spend for downloading/installation we might have much longer installation time than now with single progress bar. Instead we can start downloading resources and install them as soon as download is finished. That would let us run installation in sequence and avoid problems with running two MSI installer at the same timed. Also that would save some time and do installation for smaller components while download for big ones is in progress.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25159) Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25159:
-------------------------------------
Description:
# ASSERT: have *cdk 3.1.1* installed and running
# ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
# EXEC: install cdk 3.2.0.alpha1 and launch it
# ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
# ASSERT: *DONT* delete the server adapter for it
# EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
# EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
Result:
The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
Here's the screencast showing it: https://youtu.be/s772d9FMRIw
!image-2017-10-06-15-23-43-428.png!
Expected result:
The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
was:
# ASSERT: have *cdk 3.1.1* installed and running
# ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
# EXEC: install cdk 3.2.0.alpha1 and launch it
# ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
# ASSERT: *DONT* delete the server adapter for it
# EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
# EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
Result:
The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
!image-2017-10-06-15-23-43-428.png!
Expected result:
The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
> Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25159
> URL: https://issues.jboss.org/browse/JBIDE-25159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-06-15-23-43-428.png, image-2017-10-06-15-23-43-428.png
>
>
> # ASSERT: have *cdk 3.1.1* installed and running
> # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
> # EXEC: install cdk 3.2.0.alpha1 and launch it
> # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
> # ASSERT: *DONT* delete the server adapter for it
> # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
> # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
> Result:
> The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
> Here's the screencast showing it: https://youtu.be/s772d9FMRIw
> !image-2017-10-06-15-23-43-428.png!
> Expected result:
> The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25159) Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25159:
-------------------------------------
Workaround Description: delete defunct server adapter. Server adapter wizard will then start to show up again (and not erroneously select the defunct adapter since it thinks that there already is an adapter for the service)
Workaround: Workaround Exists
> Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25159
> URL: https://issues.jboss.org/browse/JBIDE-25159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-06-15-23-43-428.png, image-2017-10-06-15-23-43-428.png
>
>
> # ASSERT: have *cdk 3.1.1* installed and running
> # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
> # EXEC: install cdk 3.2.0.alpha1 and launch it
> # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
> # ASSERT: *DONT* delete the server adapter for it
> # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
> # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
> Result:
> The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
> !image-2017-10-06-15-23-43-428.png!
> Expected result:
> The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBDS-3756) Have two progress bars download and installation progress
by Mohit Suman (JIRA)
[ https://issues.jboss.org/browse/JBDS-3756?page=com.atlassian.jira.plugin.... ]
Mohit Suman commented on JBDS-3756:
-----------------------------------
Based on the development team discussion, we have come up with a *Single Progress Bar* for all _components_ selected for download.
Currently, every component has its own Progress bar showing the Download and Install status respectively. But as the components keep on increasing, it is not a feasible approach to display on the UI. We have made a Single Progress bar of the Download & Installation for all components selected by the user.
[~crobson] Please review and let me know if any changes needed. I have attached the video for the new progress bar UI.
> Have two progress bars download and installation progress
> ---------------------------------------------------------
>
> Key: JBDS-3756
> URL: https://issues.jboss.org/browse/JBDS-3756
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Pete Muir
> Assignee: Mohit Suman
> Priority: Minor
> Labels: ui
> Fix For: 11.x
>
>
> Most installers have a single progress bar that shows the overall progress, and then text which explains which component is being installed right now.
> Update:
> After discussion on backlog grooming session it seems reasonable to have two progress bars instead of one. Considering size of downloaded resources and time spend for downloading/installation we might have much longer installation time than now with single progress bar. Instead we can start downloading resources and install them as soon as download is finished. That would let us run installation in sequence and avoid problems with running two MSI installer at the same timed. Also that would save some time and do installation for smaller components while download for big ones is in progress.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25159) Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25159:
-------------------------------------
Description:
# ASSERT: have *cdk 3.1.1* installed and running
# ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
# EXEC: install cdk 3.2.0.alpha1 and launch it
# ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
# ASSERT: *DONT* delete the server adapter for it
# EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
# EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
Result:
The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
!image-2017-10-06-15-23-43-428.png!
Expected result:
The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
was:
# ASSERT: have *cdk 3.1.1* installed and running
# ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
# EXEC: install cdk 3.2.0.alpha1 and launch it
# ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
# ASSERT: *DONT* delete the server adapter for it
# EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
# EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
Result:
The server adapter doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
!image-2017-10-06-15-23-43-428.png!
> Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25159
> URL: https://issues.jboss.org/browse/JBIDE-25159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-06-15-23-43-428.png, image-2017-10-06-15-23-43-428.png
>
>
> # ASSERT: have *cdk 3.1.1* installed and running
> # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
> # EXEC: install cdk 3.2.0.alpha1 and launch it
> # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
> # ASSERT: *DONT* delete the server adapter for it
> # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
> # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
> Result:
> The server adapter wizard doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
> !image-2017-10-06-15-23-43-428.png!
> Expected result:
> The server adapter wizard should show up. The existing server adapter is not matching the service that is selected in the explorer.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25159) Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25159:
-------------------------------------
Summary: Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK (was: Server adapter wizard: select existing but defunct adapter instead of opening wizard after I switched CDK)
> Server adapter wizard: doesnt show up but selects existing but defunct adapter after I switched CDK
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25159
> URL: https://issues.jboss.org/browse/JBIDE-25159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.5.x
>
> Attachments: image-2017-10-06-15-23-43-428.png, image-2017-10-06-15-23-43-428.png
>
>
> # ASSERT: have *cdk 3.1.1* installed and running
> # ASSERT: have a connection, an application and a *server adapter* for this cdk (ex. an application created from nodejs-mongo-persistent template and the adapter therefore called *nodejs-mongo-persistent*
> # EXEC: install cdk 3.2.0.alpha1 and launch it
> # ASSERT: the new cdk is now on a different IP thant the one that cdk 3.1.1 used (ex. 192.168.42.207 for cdk 3.1.1, 192.168.42.20 for cdk 3.2.0.alpha1)
> # ASSERT: *DONT* delete the server adapter for it
> # EXEC: create an application from the same exmplate (ex. nodejs-mongo-persistent), do *NOT* create an adapter for it when creating the app
> # EXEC: in OpenShift explorer: select service *nodejs-mongo-persistent* and pick *Server Adapter* in the context menu.
> Result:
> The server adapter doesnt show up. Instead the "Servers" view pops up and selects the server adapter for the service that existed in the previous cdk.
> !image-2017-10-06-15-23-43-428.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months