[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21755 at 10/28/17 4:35 PM:
--------------------------------------------------------------------
This isnt the case any more. Properties are immediately available, you dont have to expand any more. Closing as OUT_OF_DATE
was (Author: adietish):
This isnt the case any more. Closing as OUT_OF_DATE
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.1.Final
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-21755.
--------------------------------------
Assignee: Andre Dietisheim (was: Xavier Coulon)
Resolution: Out of Date
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.1.Final
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21755:
------------------------------------------
This isnt the case any more. Closing as OUT_OF_DATE
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.1.Final
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21755:
-------------------------------------
Fix Version/s: 4.5.1.Final
(was: 4.5.x)
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.1.Final
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-22245) Application Wizard: Resource label key has wrong label
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22245?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22245:
------------------------------------------
The current labelling is "Name" and "Value".
!resource-labels.png!
I believe that "Key" and "Value" would be closer to the kubernetes specs as pointed out.
> Application Wizard: Resource label key has wrong label
> ------------------------------------------------------
>
> Key: JBIDE-22245
> URL: https://issues.jboss.org/browse/JBIDE-22245
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3, ux
> Fix For: 4.5.x
>
> Attachments: resource-labels.png
>
>
> In New Application wizard on the page with labels, if I select to create/edit an existing label there is opened a dialog with label details. Label consists of key:value pair (it comes from kubernetes concept), but in this labels of text widgets are "Label:" and "Value:". I think we should have it labeled as "Key:" and "Value:" instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-22245) Application Wizard: Resource label key has wrong label
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22245?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22245:
-------------------------------------
Attachment: resource-labels.png
> Application Wizard: Resource label key has wrong label
> ------------------------------------------------------
>
> Key: JBIDE-22245
> URL: https://issues.jboss.org/browse/JBIDE-22245
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3, ux
> Fix For: 4.5.x
>
> Attachments: resource-labels.png
>
>
> In New Application wizard on the page with labels, if I select to create/edit an existing label there is opened a dialog with label details. Label consists of key:value pair (it comes from kubernetes concept), but in this labels of text widgets are "Label:" and "Value:". I think we should have it labeled as "Key:" and "Value:" instead.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22259:
------------------------------------------
There's a drawback that can be worked around though: changing the rc env vars does not restart the pod it controls.
> Server Adapter: Debugging of OS 3 application creates a new replication controller
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-22259
> URL: https://issues.jboss.org/browse/JBIDE-22259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.x
>
>
> Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20730:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> Displaying of a project in OpenShift Explorer view is not consistent
> --------------------------------------------------------------------
>
> Key: JBIDE-20730
> URL: https://issues.jboss.org/browse/JBIDE-20730
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.5.x
>
>
> OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example:
> Project 01 has name: project01
> Project 02 has name: project02 and displayName: projectName02
> In OpenShift Explorer view are those projects shown as
> project01
> projectName02 (project02)
> One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this:
> project01 (project01)
> projectName02 (project02)
> because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20730:
-------------------------------------
Priority: Minor (was: Major)
> Displaying of a project in OpenShift Explorer view is not consistent
> --------------------------------------------------------------------
>
> Key: JBIDE-20730
> URL: https://issues.jboss.org/browse/JBIDE-20730
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: explorer, openshift_v3
> Fix For: 4.5.x
>
>
> OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example:
> Project 01 has name: project01
> Project 02 has name: project02 and displayName: projectName02
> In OpenShift Explorer view are those projects shown as
> project01
> projectName02 (project02)
> One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this:
> project01 (project01)
> projectName02 (project02)
> because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months