February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-72) Remove Unused JSDT Code Completion Code

by Ian Stewart-Binks (JIRA)

Ian Stewart-Binks created ERT-72: ------------------------------------ Summary: Remove Unused JSDT Code Completion Code Key: ERT-72 URL: https://issues.jboss.org/browse/ERT-72 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Ian Stewart-Binks ERT-65, ERT-66, and ERT-71 provide new implementations of an already existing code completion engine. Any code that becomes redundant due to these changes should be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-21622 at 2/2/16 11:37 AM: ---------------------------------------------------------------- Looks like a duplicate of JBIDE-21293 . And at the time people argued that this use case should never happen when this will be released - the vagrant box will never be downloaded when starting from Eclipse, it should always be downloaded beforehand - either when you install PDK, or when you install CDK. was (Author: mmalina): Looks like a duplicate of JBIDE-21293 > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Alexey Kazakov commented on TOOLSDOC-705: ----------------------------------------- {quote}"More than 60 issues targeting OpenShift 2 support have been fixed in this release of the OpenShift tooling." as far as I remember, now we are mostly working on OpenShift 3 tooling. There were not so many issues fixed for OS2, but for OS3 there were plenty of JIRAs fixed.{quote} This is a type in our N&N. We need to fix it. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21622: --------------------------------------- Looks like a duplicate of JBIDE-21293 > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Marián Labuda commented on TOOLSDOC-705: ---------------------------------------- I am bit confused. There are 2 sections, first one is for Beta2, second one for Beta1. I would suggest to swap them, bcs. Beta1 was first ;) Then there are few statements which are not quite correct I think: "More than 60 issues targeting OpenShift 2 support have been fixed in this release of the OpenShift tooling." - as far as I remember, now we are mostly working on OpenShift 3 tooling. There were not so many issues fixed for OS2, but for OS3 there were plenty of JIRAs fixed. "OpenShift 2 Server Adapter Improvements" - this headline is not ok too, the binary which is mentioned in the para right under the headline is for OS3 server adapter. Also improvements were done for OS3 server adapter. "Support for LiveReload [JBIDE-21429]" and "OpenShift Explorer Improvements [JBIDE-19178]" and "Red Hat Container Development Kit Server Adapter [JBIDE-21304]" are not made as sub-headlines, it looks as normal text. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21622: ---------------------------------------- +1. The very first start may be very long. > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21622: ----------------------------------- Fix Version/s: 4.3.1.CR1 > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21622: -------------------------------------- Assignee: Rob Stryker > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21627) Enable exposure of OpenShift resources in tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21627?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21627: --------------------------------------- I was playing with deploying of docker images lately and I found following workflow. When I have a pod and I want a service for it, I can do "oc expose pod pod-name" and it creates a service for the pod. But pod and service have still internal IP so to access to it I need another exposure "oc expose service service-name" which creates a new routing which is accessible. E.g. I was using openshift/hello-openshift image as a dummy use case and when pod was created I could not access to it yet, when service was created, I still could not access to it, but once routing is existing, it is accessible. This feature will be much more useful once JBIDE-20937 is done. That is because user could create pod from json and then create further resources (service and routing) by exposure. > Enable exposure of OpenShift resources in tooling > ------------------------------------------------- > > Key: JBIDE-21627 > URL: https://issues.jboss.org/browse/JBIDE-21627 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > > It would be nice if we would have something similar as oc binary to expose an existing resource. To expose existing pods or services. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-71) Create Relevant Methods Completion Engine

by Ian Stewart-Binks (JIRA)

Ian Stewart-Binks created ERT-71: ------------------------------------ Summary: Create Relevant Methods Completion Engine Key: ERT-71 URL: https://issues.jboss.org/browse/ERT-71 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Ian Stewart-Binks If a user invokes code completion when trying to write an object's method, relevant methods of that object *that have already been used* in the current JS file should be proposed. This should be extensible enough such that relevant methods used outside of the file can be suggested in the future as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 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 February 2016