June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20003) Explorer: Add Refresh context menu item to OpenShift v3 projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20003?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20003: ------------------------------------- Summary: Explorer: Add Refresh context menu item to OpenShift v3 projects (was: Add Refresh context menu item to OpenShift v3 projects) > Explorer: Add Refresh context menu item to OpenShift v3 projects > ---------------------------------------------------------------- > > Key: JBIDE-20003 > URL: https://issues.jboss.org/browse/JBIDE-20003 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.0.Beta2 > > > There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20003) Explorer: Add Refresh context menu item to OpenShift v3 projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20003?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20003: ---------------------------------------- Assignee: Jeff Cantrill > Explorer: Add Refresh context menu item to OpenShift v3 projects > ---------------------------------------------------------------- > > Key: JBIDE-20003 > URL: https://issues.jboss.org/browse/JBIDE-20003 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta2 > > > There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20003) Explorer: Add Refresh context menu item to OpenShift v3 projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20003?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20003: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > Explorer: Add Refresh context menu item to OpenShift v3 projects > ---------------------------------------------------------------- > > Key: JBIDE-20003 > URL: https://issues.jboss.org/browse/JBIDE-20003 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta2 > > > There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20004: ------------------------------------- Issue Type: Enhancement (was: Bug) > OpenShift v3 resources names should be camelcasized or splitted by space character > ---------------------------------------------------------------------------------- > > Key: JBIDE-20004 > URL: https://issues.jboss.org/browse/JBIDE-20004 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. > Affected resources: > * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" > * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" > * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" > * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" > I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20004: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > OpenShift v3 resources names should be camelcasized or splitted by space character > ---------------------------------------------------------------------------------- > > Key: JBIDE-20004 > URL: https://issues.jboss.org/browse/JBIDE-20004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. > Affected resources: > * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" > * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" > * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" > * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" > I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20004: ---------------------------------------- Assignee: Jeff Cantrill > OpenShift v3 resources names should be camelcasized or splitted by space character > ---------------------------------------------------------------------------------- > > Key: JBIDE-20004 > URL: https://issues.jboss.org/browse/JBIDE-20004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. > Affected resources: > * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" > * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" > * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" > * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" > I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20004: ------------------------------------------ [~jcantrill] I would think that this sounds like a worthwile improvement but I would also strive to match the web console. Do you know how the web console handles this? > OpenShift v3 resources names should be camelcasized or splitted by space character > ---------------------------------------------------------------------------------- > > Key: JBIDE-20004 > URL: https://issues.jboss.org/browse/JBIDE-20004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Priority: Minor > Fix For: 4.3.0.Beta2 > > > Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format. > Affected resources: > * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs" > * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs" > * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams" > * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers" > I would suggest to use capitalized separated wording but I leave it up to decision of developer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19692) Connection wizard: URL history contains only URLs of already existing connections

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19692?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19692: --------------------------------------- [~mlabuda] [~adietish] Is this really reasonable to recall URL's that were removed but connected to before. What if the url points to a server that no longer exists? Why would we want to remember it or keep that history. I would make the argument that if you really wanted to 'remember' a URL that you connected to previously then maybe it should be saved and not deleted. This use case has limited benefit IMO and opens us up to maintaining the associated code as well as the data that is 'saved'. > Connection wizard: URL history contains only URLs of already existing connections > --------------------------------------------------------------------------------- > > Key: JBIDE-19692 > URL: https://issues.jboss.org/browse/JBIDE-19692 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Labels: connection_wizard > Fix For: 4.3.0.Beta2 > > > URL Autocomplete/History feature implemented in JBIDE-19445 allows user to select only URLs of already existing connections (those present in OpenShift explorer view). Once the connection with some URL is removed from OpenShift explorer view, this URL is also removed from combo box of URL history. > URL autocomplete/history should remember all URL of successfully established connections even after they removal from OpenShift explorer view. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20000) Creating more readonly labels should not be possible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20000?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20000: ------------------------------------------ [~jcantrill] If I understand your description right the UI is wrong in disabling Edit/Delete for user created labels, right? Could you please add steps so that QE can replicate this? > Creating more readonly labels should not be possible > ---------------------------------------------------- > > Key: JBIDE-20000 > URL: https://issues.jboss.org/browse/JBIDE-20000 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: readonly_labels.png > > > In New application wizard for v3 connection there is a label management wizard page, where user can create/edit/remove label. It is possible to create more readonly labels, e.g. I was able to create another "template" label which already exists in table and is readonly (edit and remove button are disabled for this label). After the label is created it it not possible to edit/remove it. > !readonly_labels.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20007) AngularJS shows up in both supported and in Early Access

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20007?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-20007: --------------------------------- Attachment: EarlyAdopter_disabled.png EarlyAdopter_enabled.png > AngularJS shows up in both supported and in Early Access > -------------------------------------------------------- > > Key: JBIDE-20007 > URL: https://issues.jboss.org/browse/JBIDE-20007 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Len DiMaggio > Attachments: EarlyAdopter_disabled.png, EarlyAdopter_enabled.png > > > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

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 June 2015