[JBoss JIRA] (JBIDE-21457) Explorer: Build changes no longer update tab property view
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-21457:
-------------------------------------
Summary: Explorer: Build changes no longer update tab property view
Key: JBIDE-21457
URL: https://issues.jboss.org/browse/JBIDE-21457
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jeff Cantrill
Starting a build on the server should cause updates to appear in the build tabs. This was broken as part of making pods update correctly in the explorer view tree. Suspect it has something to do with how we find deployments for build pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20755) Import OpenShift Application wizard contains redundant validation mark
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20755 at 1/15/16 4:37 PM:
-------------------------------------------------------------------
This is very likely the very same issue as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478618 aka JBIDE-19952. An additional nested composite within the group that holds the widgets is needed (GTK3 issue).
was (Author: adietish):
This is very likely the very same issue as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478618 aka JBIDE-19952. An additional nested composite is needed.
> Import OpenShift Application wizard contains redundant validation mark
> ----------------------------------------------------------------------
>
> Key: JBIDE-20755
> URL: https://issues.jboss.org/browse/JBIDE-20755
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Fix For: 4.3.1.Beta2
>
> Attachments: validation_mark.png
>
>
> In Import OpenShift Application wizard is one validation mark (red cross) on a text widget for a git clone location in case of already imported such repo. But there is shown also another validation mark in the middle of checkbox label.
> !validation_mark.png!
> This one is redundant and also its rendering is performed only when mouse is moved over the checkbox or its label.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20755) Import OpenShift Application wizard contains redundant validation mark
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20755?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20755 at 1/15/16 4:37 PM:
-------------------------------------------------------------------
This is very likely the very same issue as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478618 aka JBIDE-19952. An additional nested composite within the group that holds the widgets is needed (GTK issue).
was (Author: adietish):
This is very likely the very same issue as in https://bugs.eclipse.org/bugs/show_bug.cgi?id=478618 aka JBIDE-19952. An additional nested composite within the group that holds the widgets is needed (GTK3 issue).
> Import OpenShift Application wizard contains redundant validation mark
> ----------------------------------------------------------------------
>
> Key: JBIDE-20755
> URL: https://issues.jboss.org/browse/JBIDE-20755
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Fix For: 4.3.1.Beta2
>
> Attachments: validation_mark.png
>
>
> In Import OpenShift Application wizard is one validation mark (red cross) on a text widget for a git clone location in case of already imported such repo. But there is shown also another validation mark in the middle of checkbox label.
> !validation_mark.png!
> This one is redundant and also its rendering is performed only when mouse is moved over the checkbox or its label.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-21143:
---------------------------------------
Linking issue as its being fixed as part of view refactor
> Triggering action on one connection refresh whole OpenShift Explorer view
> -------------------------------------------------------------------------
>
> Key: JBIDE-21143
> URL: https://issues.jboss.org/browse/JBIDE-21143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_deployment_view
> Fix For: 4.3.1.CR1
>
>
> Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-21143:
----------------------------------
Labels: explorer openshift_deployment_view (was: explorer)
> Triggering action on one connection refresh whole OpenShift Explorer view
> -------------------------------------------------------------------------
>
> Key: JBIDE-21143
> URL: https://issues.jboss.org/browse/JBIDE-21143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer, openshift_deployment_view
> Fix For: 4.3.1.CR1
>
>
> Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-21143:
-------------------------------------
Assignee: Jeff Cantrill
> Triggering action on one connection refresh whole OpenShift Explorer view
> -------------------------------------------------------------------------
>
> Key: JBIDE-21143
> URL: https://issues.jboss.org/browse/JBIDE-21143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: explorer
> Fix For: 4.3.1.CR1
>
>
> Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified in the image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21452:
------------------------------------------
docker tools cannot change the API in 4.2.1. They will therefore provide the method in the implementation but wont alter the interface. I'll thus access the method via reflection for now.
{quote}
* Xavier Coulon 3:37 PM
@FredBricon we are doing a 4.2.1 release, not 4.2 (this was in December), so we can't alter the API
@AndreDietisheim there's a work-around, though: we are going to add the method in the implementation and you'll use Reflection to call the method, even if it's not part of the API. It's a bit ugly, but that's what you'll need to do until add the method in the API for Neon.
{quote}
> Server Adapter wizard: Should use deployments-dir as specified in the image
> ---------------------------------------------------------------------------
>
> Key: JBIDE-21452
> URL: https://issues.jboss.org/browse/JBIDE-21452
> 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.3.1.Beta2
>
>
> 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)
10 years, 5 months