May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21738) Should not be able to create duplicative labels

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21738?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21738. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Should not be able to create duplicative labels > ----------------------------------------------- > > Key: JBIDE-21738 > URL: https://issues.jboss.org/browse/JBIDE-21738 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21696) New Connection wizard: Getting started info is not visible by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21696?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21696. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > New Connection wizard: Getting started info is not visible by default > ---------------------------------------------------------------------- > > Key: JBIDE-21696 > URL: https://issues.jboss.org/browse/JBIDE-21696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: default_new_conn.png, rendered_new_conn.png > > > In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection). > See screenshot of fresh opened New Connection wizard: > !default_new_conn.png! > and after checkbox is (un)checked or server type is changed: > !rendered_new_conn.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21748) Properties view: Show pod status in column for tabbed pod property

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21748?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21748. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Properties view: Show pod status in column for tabbed pod property > ------------------------------------------------------------------ > > Key: JBIDE-21748 > URL: https://issues.jboss.org/browse/JBIDE-21748 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: properties > Fix For: 4.4.0.Alpha1 > > > In new deployment view, more precisely in Properties view and tabbed property Pods, there is a table with pods under a selected project. It would be nice if there would be a column with pod status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21683) Property sheet cells are editable

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21683?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21683. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21683 > URL: https://issues.jboss.org/browse/JBIDE-21683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21562) Refresh does nothing on watch updates for deployment version of explorer view

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21562?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21562. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Refresh does nothing on watch updates for deployment version of explorer view > ----------------------------------------------------------------------------- > > Key: JBIDE-21562 > URL: https://issues.jboss.org/browse/JBIDE-21562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.4.0.Alpha1 > > > Watch and update is broken for new deployment view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-688) Rebuild JBDS-IS build to include new Drools/jBPM plugin

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/JBTIS-688?page=com.atlassian.jira.plugin.... ] Tomas David commented on JBTIS-688: ----------------------------------- One more issue from yesterday * https://issues.jboss.org/browse/DROOLS-1154. > Rebuild JBDS-IS build to include new Drools/jBPM plugin > ------------------------------------------------------- > > Key: JBTIS-688 > URL: https://issues.jboss.org/browse/JBTIS-688 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, there is Drools 6.4.0.Final. But Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. > QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. > Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21586) Explorer: Not able to delete service

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21586?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21586. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Explorer: Not able to delete service > ------------------------------------- > > Key: JBIDE-21586 > URL: https://issues.jboss.org/browse/JBIDE-21586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156 > Reporter: Xia Zhao > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3, regression > Fix For: 4.4.0.Alpha1 > > > The menuitem 'Delete Resource' disappeared on context menu of the services inside recent JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21557) Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21557?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21557. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21557 > URL: https://issues.jboss.org/browse/JBIDE-21557 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.0.Alpha1 > > > The server adapter is currently using a hard-coded deployments dir */op/app-root/src* that the user can manually edit in the wizard though. > The images now specify the deployments-dir in a label (see CLOUD-243) > {code} > com.redhat.deployments-dir > {code} > We should use this instead of the hard-coded one. > Latest docker image eap64-openshift (1.2) features the beforementioned label > ("Labels": { ... "com.redhat.deployments-dir": "/opt/eap/standalone/deployments", ... }) > {code} > -bash-4.2$ docker inspect registry.access.redhat.com/jboss-eap-6/eap64-openshift:1.2 > [ > { > "Id": "cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e", > "Parent": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134", > "Comment": "", > "Created": "2015-12-10T18:32:11.797022Z", > "Container": "", > "ContainerConfig": { > "Hostname": "", > "Domainname": "", > "User": "", > "AttachStdin": false, > "AttachStdout": false, > "AttachStderr": false, > "ExposedPorts": null, > "PublishService": "", > "Tty": false, > "OpenStdin": false, > "StdinOnce": false, > "Env": null, > "Cmd": null, > "Image": "", > "Volumes": null, > "VolumeDriver": "", > "WorkingDir": "", > "Entrypoint": null, > "NetworkDisabled": false, > "MacAddress": "", > "OnBuild": null, > "Labels": null > }, > "DockerVersion": "1.7.1", > "Author": "", > "Config": { > "Hostname": "", > "Domainname": "", > "User": "185", > "AttachStdin": false, > "AttachStdout": false, > "AttachStderr": false, > "ExposedPorts": { > "8080/tcp": {}, > "8443/tcp": {}, > "8778/tcp": {} > }, > "PublishService": "", > "Tty": false, > "OpenStdin": false, > "StdinOnce": false, > "Env": [ > "container=docker", > "PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin", > "JBOSS_IMAGE_NAME=jboss-eap-6/eap64-openshift", > "JBOSS_IMAGE_VERSION=1.2", > "JBOSS_IMAGE_RELEASE=14", > "HOME=/home/jboss", > "JAVA_TOOL_OPTIONS=-Duser.home=/home/jboss -Duser.name=jboss", > "JAVA_HOME=/usr/lib/jvm/java-1.8.0", > "JAVA_VENDOR=openjdk", > "JAVA_VERSION=1.8.0", > "LAUNCH_JBOSS_IN_BACKGROUND=true", > "JBOSS_PRODUCT=eap", > "JBOSS_EAP_VERSION=6.4.4.GA", > "JBOSS_HOME=/opt/eap", > "STI_BUILDER=jee", > "JBOSS_MODULES_SYSTEM_PKGS=org.jboss.logmanager" > ], > "Cmd": [ > "/opt/eap/bin/openshift-launch.sh" > ], > "Image": "a805aea5fb4758b2977ab4fb191f074b41d9bf751b35e0aa0e45e7d70e111134", > "Volumes": { > "/run": {} > }, > "VolumeDriver": "", > "WorkingDir": "/home/jboss", > "Entrypoint": null, > "NetworkDisabled": false, > "MacAddress": "", > "OnBuild": [], > "Labels": { > "Architecture": "x86_64", > "Authoritative_Registry": "registry.access.redhat.com", > "BZComponent": "jboss-eap-6-eap64-openshift-docker", > "Build_Host": "rcm-img-docker01.build.eng.bos.redhat.com", > "Name": "jboss-eap-6/eap64-openshift", > "Release": "14", > "Vendor": "Red Hat, Inc.", > "Version": "1.2", > "architecture": "x86_64", > "build-date": "2015-12-10T18:15:59.014349Z", > "com.redhat.deployments-dir": "/opt/eap/standalone/deployments", > "com.redhat.dev-mode": "DEBUG:true", > "com.redhat.dev-mode.port": "DEBUG_PORT:8787", > "io.k8s.description": "Platform for building and running JavaEE applications on JBoss EAP 6.4", > "io.k8s.display-name": "JBoss EAP 6.4", > "io.openshift.expose-services": "8080:http", > "io.openshift.s2i.scripts-url": "image:///usr/local/s2i", > "io.openshift.tags": "builder,javaee,eap,eap6", > "org.jboss.deployments-dir": "/opt/eap/standalone/deployments", > "vcs-ref": "f0b51e70cc004d21458ca15b1f2087ba5a6af1f7", > "vcs-type": "git" > } > }, > "Architecture": "amd64", > "Os": "linux", > "Size": 511678587, > "VirtualSize": 1206983884, > "GraphDriver": { > "Name": "devicemapper", > "Data": { > "DeviceId": "43096", > "DeviceName": "docker-253:0-268481993-cd9c11961578733a25875fb51fc94d71135cc52eb270cd58213fe99000b2ce9e", > "DeviceSize": "10737418240" > } > } > } > ] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22288) VPE crashes studio with JRE fatal error on Fedora 23

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22288?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-22288: ------------------------------------ I was able to reproduce it on my machine. Central is causing this troubles (that's why it crashes right after startup - Central is shown after startup by default), when JBDS is started with OpenJDK (i tried just one version - 8.0_91-b14). and VPE engine is JFS. When I disable Central I can start JBDS and even show some HTML file in VPE with no problem. Opening Central crashes JBDS. Running JBDS with Oracle JDK (1.8.0_65-b17) is OK. > VPE crashes studio with JRE fatal error on Fedora 23 > ---------------------------------------------------- > > Key: JBIDE-22288 > URL: https://issues.jboss.org/browse/JBIDE-22288 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.1.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: hs_err_pid2276.log.zip > > > Using VPE on Fedora ends up Studio crash > Works fine on Windows 10, Ubuntu 16.04 > More details can be found here - https://developer.jboss.org/message/955490 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22277) Auto guess Openshift connections

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22277?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22277: ------------------------------- Labels: new_and_noteworthy (was: ) > Auto guess Openshift connections > -------------------------------- > > Key: JBIDE-22277 > URL: https://issues.jboss.org/browse/JBIDE-22277 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Priority: Minor > Labels: new_and_noteworthy > Fix For: 4.4.x > > > When creating a new Openshift connection, it would be possible to provide default values for the differents fields by looking at the $HOME/.kube/config YAML files that stores various Openshift installations the user has been connected to through the Openshift oc client. > The same feature exists in the Docker tooling so this might be interesting to have the same at the Openshift side. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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