February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23817) Scaling: is not working with OpenShift 3.4 (CDK 2.4)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23817?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23817: ------------------------------------------ [~jeffmaury] thanks for preparing the grounds, your approach works perfectly. > Scaling: is not working with OpenShift 3.4 (CDK 2.4) > ---------------------------------------------------- > > Key: JBIDE-23817 > URL: https://issues.jboss.org/browse/JBIDE-23817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM2 > Environment: CDK 2.4 > Devstudio 10.3.0.AM2 > Reporter: Radim Hopp > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, scaling_pods_wizard > Fix For: 4.4.3.Final > > Attachments: Spectacle.yJ3971.png > > > Scaling pods is broken when using Openshift 3.4 from CDK 2.4. I was not able to try it with another Openshift 3.4 installation (https://open.paas.redhat.com/ is not working properly from Devstudio either - ticket INC0496390 with service-now). > When I select scale to -> and select "4" to scale to 4 pods, the pods get started but they are immediately terminated and the scaling is "1" again. > This is not happening when I used https://console.engint.openshift.com/ (OpenShift v3.3.1.4). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23897) Fix directory structure for labels in provision scripts

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-23897: ------------------------------------- Summary: Fix directory structure for labels in provision scripts Key: JBIDE-23897 URL: https://issues.jboss.org/browse/JBIDE-23897 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests Reporter: Josef Kopriva Fix directory structure for labels gnome and rh-eclipse46 in provision. These scripts have different directory structure and it should be different according to upstream project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23897) Fix directory structure for labels in provision scripts

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23897?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-23897: ------------------------------------- Assignee: Josef Kopriva > Fix directory structure for labels in provision scripts > ------------------------------------------------------- > > Key: JBIDE-23897 > URL: https://issues.jboss.org/browse/JBIDE-23897 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > > Fix directory structure for labels gnome and rh-eclipse46 in provision. These scripts have different directory structure and it should be different according to upstream project. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23896?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23896. --------------------------------- Assignee: Rob Stryker Resolution: Done pushed the change. As with all first-class properties, the user will not be able to change it directly in the launch config anymore, but will have to use the server editor (or the new wizard, for new servers) > Allow user to choose hypervisor in editor and new server wizard > --------------------------------------------------------------- > > Key: JBIDE-23896 > URL: https://issues.jboss.org/browse/JBIDE-23896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.3.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23896: ----------------------------------- Summary: Allow user to choose hypervisor in editor and new server wizard Key: JBIDE-23896 URL: https://issues.jboss.org/browse/JBIDE-23896 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, server Affects Versions: 4.4.3.AM2 Reporter: Rob Stryker Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23896) Allow user to choose hypervisor in editor and new server wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23896?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23896: -------------------------------- Fix Version/s: 4.4.3.Final > Allow user to choose hypervisor in editor and new server wizard > --------------------------------------------------------------- > > Key: JBIDE-23896 > URL: https://issues.jboss.org/browse/JBIDE-23896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, server > Affects Versions: 4.4.3.AM2 > Reporter: Rob Stryker > Fix For: 4.4.3.Final > > > Users do not like going to customize cmd args unless absolutely necessary. The most common usecases should be doable from the server editor or the creation wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19965) Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19965?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19965: -------------------------------- Priority: Optional (was: Major) > Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19965 > URL: https://issues.jboss.org/browse/JBIDE-19965 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Priority: Optional > Fix For: LATER > > > As org.eclipse.remote matures, it's worthwhile to investigate whether we should allow (experimentally) users to make use of org.eclipse.remote as their implementation of choice over RSE. > I suspect this should be done as a new set of profiles, but this would complicate the new streamlined profile-selection page in teh new server wizard, which has been outfitted with radio buttons to remove confusion and make all choices obvious. The presence of / support for two competing remote frameworks would definitely confuse the user in some ways, and so this should be approached delicately and with feedback from multiple parties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19965) Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19965?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19965: ------------------------------------- Our primary usecase for dealing with o.e.remote was the launchbar, but the launchbar opened up theri API to not be tied to o.e.remote, so this seems much less necessary. Also I'm not sure o.e.remote has been maturing much lately. > Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19965 > URL: https://issues.jboss.org/browse/JBIDE-19965 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Priority: Optional > Fix For: LATER > > > As org.eclipse.remote matures, it's worthwhile to investigate whether we should allow (experimentally) users to make use of org.eclipse.remote as their implementation of choice over RSE. > I suspect this should be done as a new set of profiles, but this would complicate the new streamlined profile-selection page in teh new server wizard, which has been outfitted with radio buttons to remove confusion and make all choices obvious. The presence of / support for two competing remote frameworks would definitely confuse the user in some ways, and so this should be approached delicately and with feedback from multiple parties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19965) Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19965?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19965: -------------------------------- Fix Version/s: LATER (was: 4.5.0.AM1) > Add profiles (or enhance "rse" profile) to allow for org.eclipse.remote as remote implementation > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19965 > URL: https://issues.jboss.org/browse/JBIDE-19965 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Fix For: LATER > > > As org.eclipse.remote matures, it's worthwhile to investigate whether we should allow (experimentally) users to make use of org.eclipse.remote as their implementation of choice over RSE. > I suspect this should be done as a new set of profiles, but this would complicate the new streamlined profile-selection page in teh new server wizard, which has been outfitted with radio buttons to remove confusion and make all choices obvious. The presence of / support for two competing remote frameworks would definitely confuse the user in some ways, and so this should be approached delicately and with feedback from multiple parties. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23870) Allow edition of Headers for a Jolokia JMX Connection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23870?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23870: ------------------------------------- [~aurelien.pupier] Is this really necessary? I'd imagine removing the header and adding a new one should suffice? > Allow edition of Headers for a Jolokia JMX Connection > ----------------------------------------------------- > > Key: JBIDE-23870 > URL: https://issues.jboss.org/browse/JBIDE-23870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > Attachments: image-2017-02-06-14-07-59-965.png > > > currently headers in Edit JMX Connection are not editable. > !image-2017-02-06-14-07-59-965.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017