May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21648: ----------------------------------- Fix Version/s: 4.3.2.Final > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Assignee: Rafael Benevides > Fix For: 4.3.2.Final, 4.4.0.Alpha2 > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21648) Add EAP 7 GA to stacks.yaml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21648?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21648: ----------------------------------- Fix Version/s: (was: 4.3.2.Final) > Add EAP 7 GA to stacks.yaml > --------------------------- > > Key: JBIDE-21648 > URL: https://issues.jboss.org/browse/JBIDE-21648 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Fred Bricon > Assignee: Rafael Benevides > Fix For: 4.4.0.Alpha2 > > > EAP 7 GA should be available from download runtime wizard. This means it should be added to stacks.yaml. > GA to be available in April 2016. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Roland Grunberg commented on JBDS-3739: --------------------------------------- I'll look into this on the Eclipse Docker Tooling end. > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22431) Rename CDK Server Adapter and other CDK ui enities

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22431?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22431: ----------------------------------- Sprint: devex #115 May 2016 > Rename CDK Server Adapter and other CDK ui enities > -------------------------------------------------- > > Key: JBIDE-22431 > URL: https://issues.jboss.org/browse/JBIDE-22431 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdk > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > We need to rename some UI stuff where CDK name is used in our tooling. > I will provide new names and the list of places where it should be changed later. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22431) Rename CDK Server Adapter and other CDK ui enities

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-22431: -------------------------------------- Summary: Rename CDK Server Adapter and other CDK ui enities Key: JBIDE-22431 URL: https://issues.jboss.org/browse/JBIDE-22431 Project: Tools (JBoss Tools) Issue Type: Task Components: cdk Reporter: Alexey Kazakov Assignee: Rob Stryker Priority: Critical Fix For: 4.4.0.Alpha3 We need to rename some UI stuff where CDK name is used in our tooling. I will provide new names and the list of places where it should be changed later. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3739: ----------------------------------- [~rgrunber] Please take the lead here at tracking down the UI freeze? > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBDS-3739 > URL: https://issues.jboss.org/browse/JBDS-3739 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: cdk, platform-installer, upstream > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Marián Labuda > Priority: Blocker > Labels: havoc > Fix For: 10.x > > Attachments: docker-frozen.txt > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21823. --------------------------------- Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-1027-B5398. > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22316) Filter template + arrow down should focus on template list and navigate through templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22316?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22316. --------------------------------- Verified in Red Hat Developer Studio with build id: Alpha1-v20160520-1027-B5398. > Filter template + arrow down should focus on template list and navigate through templates > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22316 > URL: https://issues.jboss.org/browse/JBIDE-22316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: ux > Fix For: 4.4.0.Alpha2 > > > Create a new openshift application > Type node in the filter box > Hit arrow-down to navigate through filtered nodejs items -> nothing happens. /me feels like a sad panda -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22327) Allow routes to be edited in server editor as they can in new server wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22327?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22327. --------------------------------- Closed as a duplicate. > Allow routes to be edited in server editor as they can in new server wizard > --------------------------------------------------------------------------- > > Key: JBIDE-22327 > URL: https://issues.jboss.org/browse/JBIDE-22327 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Andre Dietisheim > Fix For: 4.4.0.Alpha2 > > > See comments on https://github.com/jbosstools/jbosstools-openshift/pull/1149 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21608?page=com.atlassian.jira.plugi... ] Dmitry Bocharov reassigned JBIDE-21608: --------------------------------------- Assignee: Dmitry Bocharov > "Show In -> Web Browser via Live Reload" on EJB module should be disabled > ------------------------------------------------------------------------- > > Key: JBIDE-21608 > URL: https://issues.jboss.org/browse/JBIDE-21608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Dmitry Bocharov > Fix For: 4.4.x > > > This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled. > Rob did his part for Show in Server, but he says separate JIRAs are needed in other components. > So for Livereload, there are these two items that should be disabled on an ejb module: > Show in -> Web Browser via Livereload > Show in -> Web Browser on External device -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016