[JBoss JIRA] (JBDS-3582) JBDS installer refuses to use JDK 1.9 early access
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3582:
--------------------------------
Attachment: jbds-installer-ea.png
> JBDS installer refuses to use JDK 1.9 early access
> --------------------------------------------------
>
> Key: JBDS-3582
> URL: https://issues.jboss.org/browse/JBDS-3582
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Attachments: jbds-installer-ea.png
>
>
> It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
> We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3582) JBDS installer refuses to use JDK 1.9 early access
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3582:
--------------------------------
Description:
It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
!jbds-installer-ea.png!
was:
It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
> JBDS installer refuses to use JDK 1.9 early access
> --------------------------------------------------
>
> Key: JBDS-3582
> URL: https://issues.jboss.org/browse/JBDS-3582
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Attachments: jbds-installer-ea.png
>
>
> It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
> We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
> !jbds-installer-ea.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3582) JBDS installer refuses to use JDK 1.9 early access
by Martin Malina (JIRA)
Martin Malina created JBDS-3582:
-----------------------------------
Summary: JBDS installer refuses to use JDK 1.9 early access
Key: JBDS-3582
URL: https://issues.jboss.org/browse/JBDS-3582
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.Beta1
Reporter: Martin Malina
Assignee: Denis Golovin
It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21473) Server Adapter: Missing context menu item to show application details
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21473:
----------------------------------------
Summary: Server Adapter: Missing context menu item to show application details
Key: JBIDE-21473
URL: https://issues.jboss.org/browse/JBIDE-21473
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Marián Labuda
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.Beta2
In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21473) Server Adapter: Missing context menu item to show application details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21473?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21473:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.Beta2)
> Server Adapter: Missing context menu item to show application details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21473
> URL: https://issues.jboss.org/browse/JBIDE-21473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21473) Server Adapter: Missing context menu item to show application details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21473?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21473:
------------------------------------------
merged to master
> Server Adapter: Missing context menu item to show application details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21473
> URL: https://issues.jboss.org/browse/JBIDE-21473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, server_adapter
> Fix For: 4.4.0.Alpha1
>
>
> In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21472) Server Adapter: Missing context menu item to show application details
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21472?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21472:
-------------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.CR1)
> Server Adapter: Missing context menu item to show application details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21472
> URL: https://issues.jboss.org/browse/JBIDE-21472
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> In some commit context menu item to show application details of an OpenShift 2 application in OpenShift explorer view was changed from Application details to Properties, what is ok. But probably at same point context menu for properties/application details vanished from OpenShift 2 Server Adapter. There is no context menu "Properties" or "Application details" or any other.
--
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 a label) in the image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21452 at 1/19/16 5:27 AM:
-------------------------------------------------------------------
To be able to get inspect the image we have to first pull it which is a lengthy download. We should only do it upon user request (ex. a button "Lookup deployment directory"). Alternatively we could rsh into the pod a look for the deployments dir which would be much faster.
Another idea is to docker inspect in the pod where the image is already pulled, but then "docker" is missing in the pod/image
[~fbricon] WDYT?
was (Author: adietish):
To be able to get inspect the image we have to first pull it which is a lengthy download. We should only do it upon user request (ex. a button "Lookup deployment directory"). Alternatively we could rsh into the pod a look for the deployments dir which would be much faster.
[~fbricon] WDYT?
> Server Adapter wizard: Should use deployments-dir as specified (in a label) 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
[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified (in a label) 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:
------------------------------------------
To be able to get inspect the image we have to first pull it which is a lengthy download. We should only do it upon user request (ex. a button "Lookup deployment directory"). Alternatively we could rsh into the pod a look for the deployments dir which would be much faster.
[~fbricon] WDYT?
> Server Adapter wizard: Should use deployments-dir as specified (in a label) 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
[JBoss JIRA] (JBIDE-21452) Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21452?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21452:
-------------------------------------
Summary: Server Adapter wizard: Should use deployments-dir as specified (in a label) in the image (was: Server Adapter wizard: Should use deployments-dir as specified in the image)
> Server Adapter wizard: Should use deployments-dir as specified (in a label) 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