[JBoss JIRA] (JBDS-4409) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4409?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4409:
-----------------------------------
Sprint: devex #133 Jun 2017
> Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
> --------------------------------------------------------------------------------
>
> Key: JBDS-4409
> URL: https://issues.jboss.org/browse/JBDS-4409
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.3.0.GA
> Environment: Running on Mac 10.12.4
> JBDS
> Version: 10.3.0.GA
> Build id: GA-v20170218-1636-B94
> Build date: 20170218-1636
> Installed minishift v1.0.1
> Reporter: Veer Muchandi
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 11.0.0.AM1
>
>
> * Created a Wildfly application on openshift web-ui
> * Setup a server adapter
> * Imported application to JBDS
> * Made code changes and saved.
> Result:
> While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24184:
-------------------------------
Sprint: devex #133 Jun 2017 (was: devex #133 Jun 2017)
> Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24184
> URL: https://issues.jboss.org/browse/JBIDE-24184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}:
> * nodejs
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> ...
> {code}
> * eap
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEBUG:true",
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787",
> ...
> {code}
> Our code on the other hand is hard-coding these, not reading the keys from the docker image:
> {code}
> public class OpenShiftDebugUtils {
> private static final String DEBUG_KEY = "DEBUG";
> private static final String DEBUG_PORT_KEY = "DEBUG_PORT";
> ...
> {code}
> {code}
> public class OpenShiftLaunchController extends AbstractSubsystemController
> implements ISubsystemController, ILaunchServerController {
> ...
> private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4229) If updating CDK installation error reported
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4229?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4229:
--------------------------------
Story Points: 1
> If updating CDK installation error reported
> -------------------------------------------
>
> Key: JBDS-4229
> URL: https://issues.jboss.org/browse/JBDS-4229
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Jeff MAURY
> Labels: cdk, installer, ui
> Fix For: 11.0.0.AM1
>
> Attachments: nstall.log
>
>
> If you install DevSuite on a system where a previous version already exists, then an error is reported during the CDK installation but no explanation is given. User has to go to the install log and detect that the cdkv2 box is already there
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months