[jbosstools-issues] [JBoss JIRA] (JBDS-4777) Please document procedure (if possible) for defining Debug port, Deployment path

[André Dietisheim (Jira)]

    [ https://issues.jboss.org/browse/JBDS-4777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13746758#comment-13746758 ] 

André Dietisheim commented on JBDS-4777:
----------------------------------------

Interesting enough openshift/wildfly-160-centos7 only has the deployments-dir while the image is marked as s2i-base-container (com.redhat.component):
{code}
                "com.redhat.component": "s2i-base-container",
                "com.redhat.deployments-dir": "/wildfly/standalone/deployments",
{code}

on the other hand openshift/nodejs-010-centos7 has all 3 of them (and has no labelling for being a s2i base container):
{code}
                "com.redhat.deployments-dir": "/opt/app-root/src",
                "com.redhat.dev-mode": "DEV_MODE:false",
                "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
{code}

> Please document procedure (if possible) for defining Debug port, Deployment path
> --------------------------------------------------------------------------------
>
>                 Key: JBDS-4777
>                 URL: https://issues.jboss.org/browse/JBDS-4777
>             Project: Red Hat CodeReady Studio (devstudio)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 12.11.0.GA
>         Environment: CodeReady Studio 12.11
>            Reporter: Rick Wagner
>            Assignee: Jeff MAURY
>            Priority: Major
>              Labels: openshift
>             Fix For: 12.x
>
>         Attachments: Problem_Description.pdf
>
>
> Please document procedure for pre-filling the following in Adapter Server Settings:
> - Pod Deployment Path
> - Debugging Key
> - Debugging Port
> Can this be done via image Labels from an imported Docker image?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)